[SERVER-26145] Shutdown during move chunk commit fasserts Created: 16/Sep/16 Updated: 27/Mar/23 Resolved: 16/Sep/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.3.12 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kaloian Manassiev | Assignee: | Kaloian Manassiev |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Sprint: | Sharding 2016-10-10 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
There are certain cases where the state after a commit chunk operation is not known and the shard needs to do a majority write in order to obtain the latest config server optime. This particular write is not allowed to fail, because the shard's cached metadata and config server op time cannot be trusted. In the case where a shutdown happens at the exact time of chunk commit the shard will not continue serving requests and therefore we should special case this and not fassert. |
| Comments |
| Comment by Githook User [ 19/Sep/16 ] |
|
Author: {u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}Message: |
| Comment by Githook User [ 19/Sep/16 ] |
|
Author: {u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}Message: Revert " This reverts commit dece96ba0408446ca034a7c897ab890a80d901ef. |
| Comment by Githook User [ 19/Sep/16 ] |
|
Author: {u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}Message: |