[SERVER-35583] kill_sessions_kills_transaction.js should check for pending drop using $currentOp Created: 13/Jun/18 Updated: 29/Oct/23 Resolved: 14/Jun/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 4.0.0-rc5 |
| Fix Version/s: | 4.0.0-rc6, 4.1.1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Tess Avitabile (Inactive) | Assignee: | Tess Avitabile (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Backport Requested: |
v4.0
|
||||||||
| Sprint: | Repl 2018-06-18 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 0 | ||||||||
| Description |
|
kill_sessions_kills_transaction.js currently checks that a drop has a pending X database lock by running a find with maxTimeMS and checking that it times out. This can hang if the find is profiled, since profiling will wait for an IX database lock and does not respect maxTimeMS. Instead, we should check that the drop has a pending X database lock using a $currentOp aggregation, which does not take locks. |
| Comments |
| Comment by Githook User [ 14/Jun/18 ] |
|
Author: {'username': 'tessavitabile', 'name': 'Tess Avitabile', 'email': 'tess.avitabile@mongodb.com'}Message: (cherry picked from commit 4032e639eace4d16689ad445a8492fb9b03ddf70) |
| Comment by Githook User [ 14/Jun/18 ] |
|
Author: {'username': 'tessavitabile', 'name': 'Tess Avitabile', 'email': 'tess.avitabile@mongodb.com'}Message: |