[SERVER-20269] Make distributed-lock timeouts configurable Created: 02/Sep/15 Updated: 07/Oct/15 Resolved: 16/Sep/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding, Testing Infrastructure |
| Affects Version/s: | 3.1.7 |
| Fix Version/s: | 3.1.9 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Kamran K. | Assignee: | Esha Maharishi (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | TIG 9 (09/18/15) |
| Participants: |
| Description |
|
We'd like to be able to test distributed-lock takeover scenarios. Right now, though, the lock timeouts are set to 15 minutes, which prevents effective testing: https://github.com/mongodb/mongo/blob/r3.1.7/src/mongo/s/catalog/legacy/distlock.h#L43 Let's make the timeouts configurable with either:
|
| Comments |
| Comment by Githook User [ 16/Sep/15 ] |
|
Author: {u'name': u'Esha Maharishi', u'email': u'esha.maharishi@mongodb.com'}Message: Closes #1019 Signed-off-by: Kamran Khan <kamran.khan@mongodb.com> |
| Comment by Andy Schwerin [ 03/Sep/15 ] |
|
Fail points, please. |