[SERVER-8690] node marked as ok before marked as secondary by ReplicaSetMonitorWatcher Created: 24/Feb/13  Updated: 10/Dec/14  Resolved: 24/Jan/14

Status: Closed
Project: Core Server
Component/s: Internal Client, Replication
Affects Version/s: 2.4.0-rc0
Fix Version/s: None

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

Issue Links:
Duplicate
duplicates SERVER-12221 Sleep in ReplicaSetMonitor::_check is... Closed
Operating System: ALL
Participants:

 Description   

also assume this can happen in other related mongos node checks.

This causes strange behavior when a replica set is temporarily detected as down because the primary has broken connections - if operations are occurring while the ReplicaSetMonitorWatcher is refreshing the view of the replica set, the node is marked as "ok" and the old primary is assumed to be the current primary for a short period of time.


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