[DOCS-3914] MMS OnPrem1.5 : Release notes Created: 17/Aug/14  Updated: 16/Mar/15  Resolved: 29/Aug/14

Status: Closed
Project: Documentation
Component/s: Cloud Manager
Affects Version/s: None
Fix Version/s: v1.3.10, mms-1.5

Type: Task Priority: Major - P3
Reporter: Cailin Nelson Assignee: Sam Kleinman (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Participants:
Days since reply: 9 years, 26 weeks, 3 days ago

 Description   

Considerations for Upgrade

  • Direct upgrades are supported only from 1.3 and 1.4.
  • Change in configurations and policy for 2FA
    • Two-factor authentication must now be explicitly enabled using the mms.multiFactorAuth.require setting. See [LINK TO DOCS]
  • The default LDAP group separator was changed from , to ;; . See [LINK TO DOCS]
  • Suppressed hosts will only remain suppressed for 30 minutes
    • Previously, if a host was deleted from MMS Monitoring the hostname/port would be added to a suppression list with an infinite lifetime. This was meant to prevent a race condition in which a host in a cluster would be auto-discovered by another member of a cluster before the cluster could fully be removed.
    • Suppressed hosts are now kept on this list for only 30 minutes.
  • mms.remoteIp.header in conf-mms.properties should be set if MMS is behind a load balancer
  • mongo.backupdb.mongoUri is no longer in conf-mms.properties. This was previously a required field in this file. It is still in the backup daemons's conf-daemon.properties.
  • Stored MongoDB profile data is not transferred between OnPrem 1.4 and OnPrem 1.5
    • If the optional feature to collect and store MongoDB profile data in MMS was enabled, this data will not be transferred between OnPrem 1.4 and OnPrem 1.5.

Improvements

  • When an MMS Backup job fails to bind, the system will periodically and automatically retry
  • All MMS Backup jobs will retry indefinitely
  • Point in Time restores can be selected with one second granularity

New Features

  • Public API http://mms.mongodb.com/help/reference/api/ currently, need to be visible on help-hosted
  • Explicit support for multiple MMS Backup Blockstore Databases and the ability to pin MMS Groups to specific backup daemons and databases. [LINK TO DOCS]
  • MMS can authenticate using LDAP to both the database backing MMS and the databases being monitored/backed up [LINK TO DOCS]
  • Enhanced auditing [LINK TO DOCS]
  • Ability to acknowledge alerts
  • New cluster page - shows individual, sum or average metrics for all shards in a cluster

Agents

  • Monitoring Agent 2.4.2.113 Release Notes
    • Upgraded agent to use Go 1.3.
    • Updated mgo driver, which includes fix for MGO-34. All DNS lookups should now timeout appropriately.
    • Added support for connecting to hosts using LDAP authentication.
    • Added support for version and -version.
    • Agent now displays git commit hash of Monitoring Agent in the log file.
    • Updates to the configuration file format.
  • Backup Agent 2.3.1.160 Release Notes
    • Backup Agent now sends oplog slices in batches
    • Improved stability around oplog tokens for environments with unstable networks.
    • Support for a new API that allows MMS to ingest oplog entries before the entire payload has reached the MMS servers.
    • Upgraded agent to use to Go 1.3
    • Added support for version and -version.
    • Added support for connecting to hosts using LDAP authentication.
    • Agent now provides additional logging information when the Backup Agent manipulates the balancer.
    • Agent now supports configuring HTTP proxies with the config file.

Generated at Thu Feb 08 07:46:47 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.