[SERVER-3959] Dist lock not relinquished in the event of failover Created: 27/Sep/11 Updated: 11/Jul/16 Resolved: 04/Oct/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 2.0.0 |
| Fix Version/s: | 2.0.1, 2.1.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kyle Banker | Assignee: | Greg Studer |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||
| Issue Links: |
|
||||
| Operating System: | ALL | ||||
| Participants: | |||||
| Description |
|
It seems that if a primary takes a lock and then fails over in the middle of a migration, the lock isn't relinquished. |
| Comments |
| Comment by auto [ 04/Oct/11 ] |
|
Author: {u'login': u'gregstuder', u'name': u'gregs', u'email': u'greg@10gen.com'}Message: Change test to allow the creation of new locks as well |
| Comment by auto [ 04/Oct/11 ] |
|
Author: {u'login': u'gregstuder', u'name': u'gregs', u'email': u'greg@10gen.com'}Message: share lastpings between dist locks |
| Comment by auto [ 04/Oct/11 ] |
|
Author: {u'login': u'gregstuder', u'name': u'gregs', u'email': u'greg@10gen.com'}Message: Change test to allow the creation of new locks as well |
| Comment by auto [ 29/Sep/11 ] |
|
Author: {u'login': u'gregstuder', u'name': u'gregs', u'email': u'greg@10gen.com'}Message: share lastpings between dist locks |
| Comment by Greg Studer [ 29/Sep/11 ] |
|
Test for unlocking behavior. |