[SERVER-4505] Don't assume old primary is still primary when no nodes are returning isMaster Created: 15/Dec/11  Updated: 11/Jul/16  Resolved: 17/May/12

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

Type: Bug Priority: Major - P3
Reporter: Spencer Brody (Inactive) Assignee: Spencer Brody (Inactive)
Resolution: Done Votes: 0
Labels: 212push
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-5642 Make mongobridge work with ShardingTe... Closed
Related
is related to SERVER-4661 Mongos doesn't detect primary change ... Closed
Operating System: ALL
Participants:

 Description   

If a shard's primary steps down, but the mongos can't connect to the new primary, the mongos continues thinking that the old primary is still the master. This will cause it to send setShardVersion commands to the former primary, which will fail and be retried many times.



 Comments   
Comment by Ian Whalen (Inactive) [ 17/May/12 ]

Creating new ticket to track creation of additional tests.

Comment by auto [ 19/Apr/12 ]

Author:

{u'login': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@10gen.com'}

Message: Don't assume old primary is still primary when no nodes are returning isMaster. SERVER-4505
Branch: master
https://github.com/mongodb/mongo/commit/f118b7bb4842dc9d09f9ec445514d3e793ec333c

Comment by Spencer Brody (Inactive) [ 10/Apr/12 ]

Increased time estimate because while the actual fix is small, testing requires non-trivial additions to our test infrastructure.

Comment by Spencer Brody (Inactive) [ 10/Apr/12 ]

Need failpoints from SERVER-5175 (or something similar) to be able to test network connectivity loss.

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