Details
-
Bug
-
Status: Closed
-
Major - P3
-
Resolution: Works as Designed
-
None
-
None
-
None
-
ALL
Description
If you have a weird distribution of votes in a system, you can have a situation where a write succeeds with w:majority but disappears after a failover. For example:
{ _id : "myrs",
|
members : [ { _id : "0", host : "A", votes: 1 },
|
{ _id : "1", host : "B", votes: 1 },
|
{ _id : "2", host : "C", votes: 3 } ] }
|
Suppose w:majority write reaches "A" and "B" but not "C", so the client gets the confirmation; and then "A" and "B" both fail simultaneously. "C" will elect itself primary, but not have the write.
If the goal of w:majority is to give people the guarantee that the write will remain despite any failure that nonetheless leaves the replica set with a primary, then w:majority should be vote-aware.
Alternatively, we should get rid of votes.
EDIT: We will be deprecating member votes that are not 0 or 1.
Attachments
Issue Links
- is related to
-
SERVER-3110 unlimited nonvoting nodes in replica set
-
- Closed
-
-
SERVER-10513 deprecate votes in replica set config
-
- Closed
-
-
-
- Closed
-
- related to
-
-
- Closed
-