[SERVER-9989] rs.status() when issued from a Secondary can still show a Primary with syncingTo Created: 21/Jun/13  Updated: 11/Jul/16  Resolved: 21/Jun/13

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

Type: Bug Priority: Major - P3
Reporter: Andre de Frere Assignee: Matt Dannenberg
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
Backwards Compatibility: Fully Compatible
Operating System: ALL
Steps To Reproduce:
  1. Connect to the Primary
  2. rs.stepDown()
  3. Connect to the new Primary
  4. rs.stepDown()
  5. connect to another secondary
  6. rs.status() will show the old Primary with a syncingTo field
Participants:

 Description   

If the current Primary of a replica set has been a Secondary in the past, then a rs.status() when issued from a current Secondary will show that Primary with a syncingTo field.



 Comments   
Comment by auto [ 21/Jun/13 ]

Author:

{u'username': u'dannenberg', u'name': u'matt dannenberg', u'email': u'matt.dannenberg@10gen.com'}

Message: SERVER-9989 remove syncingTo field from rs.status when that member is no longer syncing from anyone
Branch: master
https://github.com/mongodb/mongo/commit/c42fd35a0a0bd5f9511fdcbea4bdc2ec590fddd3

Generated at Thu Feb 08 03:21:58 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.