[SERVER-38474] Make ReplSetDistLockManager::shutDown interruptible Created: 07/Dec/18 Updated: 29/Oct/23 Resolved: 20/Dec/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.7 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Siyuan Zhou | Assignee: | Kim Tao |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | prepare_interruptibility, uninterruptibleLockGuardRemoval | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Sharding 2018-12-31 | ||||||||
| Participants: | |||||||||
| Description |
|
Sharding calls stopPing() at shutdown. findAndModify remove through DBDirectClient. If this can cause an implicit collection creation accidentally, it would take a stronger lock, so it may conflict with prepared transactions. We need to make sure it's interruptible. |
| Comments |
| Comment by Githook User [ 20/Dec/18 ] |
|
Author: {'username': 'Kimchelly', 'email': 'kimberly.tao@mongodb.com', 'name': 'Kim Tao'}Message: |