[SERVER-67986] Wait for recipients to reach block timestamp asynchronously Created: 12/Jul/22 Updated: 13/Oct/23 Resolved: 13/Oct/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Matt Broadstone | Assignee: | Didier Nadeau |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Serverless
|
||||||||
| Participants: | |||||||||
| Description |
|
The ShardSplitDonorService currently waits for recipient nodes to reach the blockTimestamp synchronously. Use the asynchronous awaitReplicationAsyncNoWTimeout instead. |
| Comments |
| Comment by Didier Nadeau [ 13/Oct/23 ] |
|
Closing as won't do for now as there hasn't been any change on SERVER-69221 in a year. |
| Comment by Matt Broadstone [ 28/Aug/22 ] |
|
I tried to make this change, but then realized that awaitReplicationAsyncNoWTimeout does not accept a cancellation token. I filed SERVER-69221 to track adding support for a cancellation token in a repl API for awaiting replication. |