[SERVER-13993] log a message when shouldChangeSyncTarget() believes a node should change sync targets Created: 19/May/14  Updated: 11/Mar/15  Resolved: 19/May/14

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: 2.6.1
Fix Version/s: 2.6.2, 2.7.1

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

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Backport Completed:
Participants:

 Description   

a user hit a strange issue involving an infinite loop of attempting to resync delayed secondaries from other delayed secondaries and a message here would have made debugging it trivial



 Comments   
Comment by Githook User [ 25/May/14 ]

Author:

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

Message: SERVER-13993 log the decision to change sync targets

(cherry picked from commit e84c75764bd1b1b1700cb30599c6dd2aee34eba2)
Branch: v2.6
https://github.com/mongodb/mongo/commit/9a9b2e504d3c9cbbf4d9f58a1ff0e16c53719169

Comment by Ramon Fernandez Marina [ 20/May/14 ]

Author:

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

Message: SERVER-13993 log the decision to change sync targets

Branch: master
https://github.com/mongodb/mongo/commit/e84c75764bd1b1b1700cb30599c6dd2aee34eba2

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