[SERVER-50656] Add cancelation support to WaitForMajorityService using CancelationTokens Created: 31/Aug/20 Updated: 29/Oct/23 Resolved: 18/Mar/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Code |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0 |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Matthew Saltz (Inactive) | Assignee: | George Wangensteen |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||
| Sprint: | Service arch 2020-12-28, Service Arch 2021-03-08, Service Arch 2021-03-22 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Linked BF Score: | 120 | ||||||||||||||||||||
| Story Points: | 3 | ||||||||||||||||||||
| Description |
|
waitUntilMajority should accept a CancelationToken. When the token is canceled, it should remove the appropriate OpTime from this map and the request's future must be signalled, but only if this was the only request pointing to that OpTime. This may require us to change from using SharedPromise to instead use something like a multimap with multiple promises/futures per OpTime. |
| Comments |
| Comment by Githook User [ 17/Mar/21 ] |
|
Author: {'name': 'George Wangensteen', 'email': 'george.wangensteen@mongodb.com', 'username': 'gewa24'}Message: |
| Comment by Githook User [ 04/Feb/21 ] |
|
Author: {'name': 'George Wangensteen', 'email': 'george.wangensteen@mongodb.com', 'username': 'gewa24'}Message: Revert " This reverts commit da77452821c355346d873a6b31160c101adc60de. |
| Comment by Githook User [ 04/Feb/21 ] |
|
Author: {'name': 'George Wangensteen', 'email': 'george.wangensteen@mongodb.com', 'username': 'gewa24'}Message: |