[SERVER-71792] Log list of cursors a range deletion is going to wait on Created: 02/Dec/22 Updated: 29/Oct/23 Resolved: 09/Feb/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.0.0-rc0, 6.3.0-rc1, 6.0.6 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Pierlauro Sciarelli | Assignee: | Pierlauro Sciarelli |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | sharding-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Sharding EMEA
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Backport Requested: |
v6.3, v6.0
|
||||||||||||
| Sprint: | Sharding EMEA 2023-01-23, Sharding EMEA 2023-02-06, Sharding EMEA 2023-02-20 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
Purpose of this ticket is to add the information and evaluate whether to build a more complex machinery to not only log cursors when a range deletion starts, but also after it has been waiting for a long time. The solution must add the info in the code paths of the legacy range deleter (for pre-6.2.0 versions) and the new range deleter service. |
| Comments |
| Comment by Githook User [ 21/Apr/23 ] |
|
Author: {'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}Message: |
| Comment by Githook User [ 20/Feb/23 ] |
|
Author: {'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}Message: |
| Comment by Githook User [ 09/Feb/23 ] |
|
Author: {'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}Message: |