[SERVER-24842] ShardingStateRecovery::recover cleanup should not wait for replication Created: 29/Jun/16 Updated: 21/Nov/16 Resolved: 05/Jul/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.2.7, 3.3.9 |
| Fix Version/s: | 3.2.9, 3.3.10 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kaloian Manassiev | Assignee: | Kaloian Manassiev |
| Resolution: | Done | Votes: | 0 |
| Labels: | code-only | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Backport Completed: | |
| Sprint: | Sharding 17 (07/15/16) |
| Participants: |
| Description |
|
Upon success the ShardingStateRecovery::recover call tries to cleanup the recovery document and uses majority write concern to do that. This method is called at the end of draining mode, but still under the global X lock and as a result it will never replicate and will stall leaving the draining mode. Instead, ShardingStateRecovery::recover should use local-only write concern. |
| Comments |
| Comment by Githook User [ 29/Jul/16 ] |
|
Author: {u'username': u'visemet', u'name': u'Max Hirschhorn', u'email': u'max.hirschhorn@mongodb.com'}Message: |
| Comment by Githook User [ 29/Jul/16 ] |
|
Author: {u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}Message: |
| Comment by Githook User [ 28/Jul/16 ] |
|
Author: {u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}Message: Revert " This reverts commit 53f346b85633e206f00b3c5cdd702a7ef3e90095. |
| Comment by Githook User [ 28/Jul/16 ] |
|
Author: {u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}Message: |
| Comment by Githook User [ 05/Jul/16 ] |
|
Author: {u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}Message: |