[SERVER-18951] dassert in waitForWriteConcern fails when w:majority adds j:true with journaling off Created: 12/Jun/15 Updated: 19/Sep/15 Resolved: 22/Jul/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 3.1.7 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Spencer Brody (Inactive) | Assignee: | Eric Milkie |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Sprint: | RPL 7 08/10/15 |
| Participants: |
| Description |
|
Once users upgrade to the new election protocol we will start automatically adding j:true to any w:majority writes. This could trigger a dassert on debug builds if journaling is off because we will consider the write concern with j:true to not be valid since journaling is disabled. I think to fix this, we should not append j:true to w:majority writes if journaling is disabled. |
| Comments |
| Comment by Githook User [ 28/Jul/15 ] |
|
Author: {u'username': u'milkie', u'name': u'Eric Milkie', u'email': u'milkie@10gen.com'}Message: |
| Comment by Githook User [ 22/Jul/15 ] |
|
Author: {u'username': u'milkie', u'name': u'Eric Milkie', u'email': u'milkie@10gen.com'}Message: |
| Comment by Eric Milkie [ 17/Jul/15 ] |
|
We'll work on it first thing. |