[SERVER-20037] Transfer responsibility for the release of distributed locks to new catalog manager Created: 19/Aug/15 Updated: 25/Jan/17 Resolved: 12/Jan/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 3.2.3, 3.3.1 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Andy Schwerin | Assignee: | Spencer Brody (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | code-only, csrsupgrade | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Backport Completed: | |||||||||||||||||
| Sprint: | Sharding 9 (09/18/15), Sharding E (01/08/16), Sharding F (01/29/16) | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
When replacing the actual sharding catalog manager in a mongo process, the old manager will shut down without being able to release any distributed locks it holds. The new manager should release all locks held by the old manager, since all operations undertaken by the old manager that are not yet complete must have been aborted. |
| Comments |
| Comment by Githook User [ 14/Jan/16 ] |
|
Author: {u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}Message: (cherry picked from commit f2d33bbcde359f5caf2e4e66559dcc46b164cd2b) |
| Comment by Githook User [ 14/Jan/16 ] |
|
Author: {u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}Message: (cherry picked from commit dd0e551071e7128d48d01455e332e30beaa63244) |
| Comment by Githook User [ 12/Jan/16 ] |
|
Author: {u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}Message: |
| Comment by Githook User [ 06/Jan/16 ] |
|
Author: {u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}Message: |