[SERVER-63020] Investigate relevance of SERVER-31978 to per shard cursors Created: 26/Jan/22 Updated: 16/Feb/22 Resolved: 16/Feb/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Mickey Winters | Assignee: | Jennifer Peshansky (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Sprint: | QE 2022-02-21 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
I stumbled across this comment which mentioned the linked ticket and seems to imply there may be issues with arm not being prepared for a cursor to close prematurely. Per shard change stream cursors don't need to coordinate across shards so some of these warnings may be irrelevant. |
| Comments |
| Comment by Jennifer Peshansky (Inactive) [ 16/Feb/22 ] |
|
After discussion with Charlie and Bernard, it seems that this invariant is no longer relevant, since DocumentSourceCloseCursor has been removed. The invariant and the comment are probably safe to delete, and the Per Shard Cursors project doesn't need to worry about it. I've filed |