[SERVER-48276] ReplSet Free Monitoring URLs inconsistent Created: 18/May/20  Updated: 29/Oct/23  Resolved: 29/May/20

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 4.0.20, 4.2.8, 4.4.0-rc8, 4.7.0

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

Attachments: PNG File AllMembersAfterRestarting.png     HTML File Ouputs     PNG File PrimaryAfterEnablingFreeMonitoring.png    
Issue Links:
Backports
Depends
is depended on by SERVER-48275 ReplSet Free Monitoring URLs inconsis... Closed
Related
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.4, v4.2, v4.0
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)
Sprint: Security 2020-06-01
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)


 Comments   
Comment by Mark Benvenuto [ 02/Jun/20 ]

Branch v4.2
https://github.com/mongodb/mongo/commit/2b79d62349c657fed185af00ba5d93a1032feb69

Comment by Githook User [ 02/Jun/20 ]

Author:

{'name': 'Mark Benvenuto', 'email': 'mark.benvenuto@mongodb.com', 'username': 'markbenvenuto'}

Message: SERVER-48276 ReplSet Free Monitoring URLs inconsistent

(cherry picked from commit 4ec400290afe55c470cb14fbafb79e9f649d7cb1)
Branch: v4.0
https://github.com/mongodb/mongo/commit/be78a43c50cde0844d114249cc45b6102b4cd6c8

Comment by Githook User [ 02/Jun/20 ]

Author:

{'name': 'Mark Benvenuto', 'email': 'mark.benvenuto@mongodb.com', 'username': 'markbenvenuto'}

Message: SERVER-48276 ReplSet Free Monitoring URLs inconsistent

(cherry picked from commit 4ec400290afe55c470cb14fbafb79e9f649d7cb1)
Branch: v4.4
https://github.com/mongodb/mongo/commit/a0c55b0db33e2a3ca23fe8c994ce1045677d6ca6

Comment by Githook User [ 29/May/20 ]

Author:

{'name': 'Mark Benvenuto', 'email': 'mark.benvenuto@mongodb.com', 'username': 'markbenvenuto'}

Message: SERVER-48276 ReplSet Free Monitoring URLs inconsistent
Branch: master
https://github.com/mongodb/mongo/commit/4ec400290afe55c470cb14fbafb79e9f649d7cb1

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