[SERVER-48275] ReplSet Free Monitoring URLs inconsistent Created: 18/May/20  Updated: 18/May/20  Resolved: 18/May/20

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Isabel Peters Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-48276 ReplSet Free Monitoring URLs inconsis... Closed
Operating System: ALL
Steps To Reproduce:
  • Start a replica set with above mentioned version
  • enable free monitoring on the primary
  • connect to secondaries - should have different URLs
  • URL should each show an individual output rather than the output of all members
  • Restart replica set
  • URL of primary shows all expected members
  • Secondaries also show expected URL (of primary)
Participants:

 Description   

Tested versions this is happening on: 4.0.18, 4.4.0-rc5, 4.4.0-rc6 (and some 4.2)
After creating a new replica set (5 nodes) and enabling free monitoring by running
db.enableFreeMonitoring() on the primary, a new URL for the free-monitoring service is created. The URL displays the stats for the primary node only (see attached screenshot). All secondaries show a different URL when connecting to them on the shell.

Expected:

  • The URL of the primary should have replicated to the secondaries so that they all point to the same URL.
  • The visual free monitoring view should have displayed all 5 nodes (stats) of the entire replica set

Note that:

  • After restarting the replica set (with free monitoring enabled) the primary URL is propagated to all secondaries and the view is correct
  • Tested on 4.0.0 and works as expected (primary URL is propagated to secondaries)

Attached:

  • outputs from the shell for initial URLs of primary and a secondary and after restarting
  • Screenshot of visual output after enabling free monitoring (primary)
  • Screenshot of visual output after restarting the replica set (expected output)

Generated at Thu Feb 08 05:16:38 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.