[SERVER-24781] DistLockManager on the CSRS primary should be able to re-acquire locks immediately after promotion Created: 24/Jun/16 Updated: 19/Jul/16 Resolved: 07/Jul/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 3.3.10 |
| Type: | Bug | 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: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Sprint: | Sharding 17 (07/15/16) | ||||||||
| Participants: | |||||||||
| Description |
|
With more and more sharding metadata management is moving from mongos to the CSRS primary, if a stepdown happens while that CSRS primary is holding any distributed locks, it will not be able to release them and they will be stuck for 15+ minutes. We should add capability for the local DistLockManager to be able to inherit the locks after recovery. |
| Comments |
| Comment by Githook User [ 07/Jul/16 ] |
|
Author: {u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}Message: This also reverts commit cc904854866b1cd1a25508573eeab322c0dacbff. |
| Comment by Githook User [ 24/Jun/16 ] |
|
Author: {u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}Message: This change reverts to the old (pre-3.3) behaviour where the shard is It is done in order to stabilize the continuous stepdown suite and will be |