[DOCS-14803] Document that Range Deleter can be blocked due to ongoing read operations on the target collection (open cursors) Created: 17/Sep/21 Updated: 30/Oct/23 Resolved: 20/Sep/21 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Dmitry Ryabtsev | Assignee: | Jeffrey Allen |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 2 years, 20 weeks, 2 days ago |
| Epic Link: | DOCSP-11702 |
| Story Points: | 3 |
| Description |
|
From the current state of the docs it is not obvious that Range Deleter may not be able to progress if there are long running read operations / open cursors on the collection the deletes should be run on. We should clarify this aspect so the effect of balancing can be more predictable for the users. |
| Comments |
| Comment by Githook User [ 20/Sep/21 ] |
|
Author: {'name': 'Jeff Allen', 'email': 'jeffrey.allen@10gen.com', 'username': 'jeff-allen-mongo'}Message: ( |
| Comment by Githook User [ 20/Sep/21 ] |
|
Author: {'name': 'Jeff Allen', 'email': 'jeffrey.allen@10gen.com', 'username': 'jeff-allen-mongo'}Message: ( |
| Comment by Githook User [ 20/Sep/21 ] |
|
Author: {'name': 'Jeff Allen', 'email': 'jeffrey.allen@10gen.com', 'username': 'jeff-allen-mongo'}Message: ( |
| Comment by Dmitry Ryabtsev [ 18/Sep/21 ] |
|
Hi jeffrey.allen that seems like an appropriate place. Thanks. |
| Comment by Jeffrey Allen [ 17/Sep/21 ] |
|
Hi dmitry.ryabtsev, thanks for filing this ticket. We could mention this behavior in the Range Deletion Performance Tuning section. Do you think that's the right place to mention this info? |