[SERVER-24858] Tighten assertions around waiting for write concern Created: 30/Jun/16 Updated: 26/Oct/16 Resolved: 08/Jul/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 3.3.10 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Kaloian Manassiev | Assignee: | Kaloian Manassiev |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Minor Change | ||||||||||||||||
| Sprint: | Sharding 17 (07/15/16) | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
In certain situations it is illegal to wait for write concern, such as while holding X lock on the local database. We should tighten these assertions so we catch offending callers. In addition, as part of this change we should not allow write concern other than majority for config servers. |
| Comments |
| Comment by Githook User [ 11/Jul/16 ] |
|
Author: {u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}Message: |
| Comment by Githook User [ 08/Jul/16 ] |
|
Author: {u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}Message: |
| Comment by Andy Schwerin [ 02/Jul/16 ] |
|
It should be illegal to wait for write concern while holding the global lock in any mode, as it can involve network activity. |