[SERVER-3020] distributed lock rapid reacquire in balancer... Created: 29/Apr/11 Updated: 12/Jul/16 Resolved: 29/Apr/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 1.9.0 |
| Fix Version/s: | 1.9.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Greg Studer | Assignee: | Eliot Horowitz (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
... which leads to long delays if the lock is rapidly unlocked and then tried for reacquire (which seems to safely fail if done immediately after unlock) solution - retry lock if no error after 1s delay? |
| Comments |
| Comment by auto [ 29/Apr/11 ] |
|
Author: {u'login': u'erh', u'name': u'Eliot Horowitz', u'email': u'eliot@10gen.com'}Message: don't sleep with lock held |