[SERVER-59641] Oplog fetching should not obtain read tickets Created: 27/Aug/21 Updated: 27/Oct/21 Resolved: 27/Oct/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | 4.0.24 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Xuerui Fa | Assignee: | Benety Goh |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Sprint: | Execution Team 2021-11-01 | ||||||||||||
| Participants: | |||||||||||||
| Case: | (copied to CRM) | ||||||||||||
| Description |
|
Currently, if read tickets are exhausted on a node, replication will stall for any secondaries syncing from that node. Ideally, oplog fetching should still make progress. Would it be possible for oplog fetching readers to bypass obtaining a read ticket? |
| Comments |
| Comment by Benety Goh [ 27/Oct/21 ] |
|
This ticket has been fixed in 5.0 - see The issue described in this ticket was reported against a 4.0 server. Closing this as a duplicate of |
| Comment by Connie Chen [ 15/Oct/21 ] |
|
We should not include changestreams for this ticket. |