[SERVER-33576] Remove UninterruptibleLockGuards in replication code to allow interruptible lock acquisition Created: 01/Mar/18 Updated: 29/Oct/23 Resolved: 14/Mar/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 3.7.3 |
| Fix Version/s: | 3.7.4 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Louis Williams | Assignee: | Spencer Brody (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Repl 2018-03-26 |
| Participants: |
| Description |
|
Since The following places in the replication code have temporary UninterruptibleLockGuard s to prevent crashing due to inadequate exception handling: src/mongo/db/repl/master_slave.cpp:886 |
| Comments |
| Comment by Spencer Brody (Inactive) [ 14/Mar/18 ] |
|
The master-slave code has been removed, and the UninterruptableLockGuard in replication coordinator is used in stepdown, where it is something we'll want to keep around indefinitely. I did, however, reduce the scope of the guard for just the one part of stepDown that needs it. |
| Comment by Githook User [ 14/Mar/18 ] |
|
Author: {'email': 'spencer@mongodb.com', 'name': 'Spencer T Brody', 'username': 'stbrody'}Message: |