[SERVER-48502] Tighten $currentOp and pinned cursor checks in kill_pinned_cursor.js Created: 29/May/20 Updated: 29/Oct/23 Resolved: 02/Jun/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.4.0-rc8, 4.4.0-rc9, 4.7.0, 4.2.11 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Nicholas Zolnierz | Assignee: | Nicholas Zolnierz |
| 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.4, v4.2
|
||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Linked BF Score: | 17 | ||||||||||||||||||||
| Description |
|
The test is assuming a find command is hitting a fail point for a pinned cursor by looking at the total open 'pinned' count in serverStatus. However, its possible that other background threads (e.g. PeriodicShardedIndexConsistencyChecker) hit the fail point and not the find command that the test is expecting. Instead of using serverStatus, the test should run a $currentOp and filter the output based on the 'failpointMsg' and the 'comment' string. |
| Comments |
| Comment by Githook User [ 06/Oct/20 ] |
|
Author: {'name': 'Ian Boros', 'email': 'ian.boros@mongodb.com', 'username': 'puppyofkosh'}Message: |
| Comment by Githook User [ 05/Oct/20 ] |
|
Author: {'name': 'Ian Boros', 'email': 'ian.boros@mongodb.com', 'username': 'puppyofkosh'}Message: |
| Comment by Githook User [ 02/Jun/20 ] |
|
Author: {'name': 'Nick Zolnierz', 'email': 'nicholas.zolnierz@mongodb.com', 'username': 'nzolnierzmdb'}Message: |