[SERVER-26908] rc-2 repl set stops being able to fulfill majority write concern Created: 04/Nov/16 Updated: 31/Jan/17 Resolved: 23/Jan/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kay Kim (Inactive) | Assignee: | Judah Schvimer |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
|||||||||||||
| Issue Links: |
|
|||||||||||||
| Operating System: | ALL | |||||||||||||
| Steps To Reproduce: | 1) 3 member repl set (nothing special)
was successful 5) c=rs.conf() 6) c.protocolVersion=0 7) rs.reconfig(c) 8) c=rs.status() 9) c=rs.conf() 10) c.protocolVersion=1 11) rs.reconfig(c) 12) rs.status() 13)
returns
|
|||||||||||||
| Sprint: | Repl 2017-02-13 | |||||||||||||
| Participants: | ||||||||||||||
| Description |
|
with pv1, I first did
and was successful.
*note* I didn't change writeConcernMajorityJournalDefault during any of my shenanigans. |
| Comments |
| Comment by Judah Schvimer [ 23/Jan/17 ] |
|
Per our discussion, we are not concerned by this bug and closing as "Won't Fix". |
| Comment by Spencer Brody (Inactive) [ 08/Dec/16 ] |
|
Judah, please do a RCA so we can understand if the root cause is likely to manifest in any other ways. |
| Comment by Spencer Brody (Inactive) [ 08/Nov/16 ] |
|
Repro'd on master and 3.2 branch as well. |
| Comment by Spencer Brody (Inactive) [ 08/Nov/16 ] |
|
Attaching jstests that repro's the issue |
| Comment by Spencer Brody (Inactive) [ 08/Nov/16 ] |
|
kay.kim, I wasn't able to repro this - what happens if you turn the wtimeout up a bunch to say 30 seconds, does the issue still happen? |