[SERVER-63090] Recipient garbarge collects itself on primary step up Created: 28/Jan/22 Updated: 29/Oct/23 Resolved: 09/Mar/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.0.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Matt Broadstone | Assignee: | Mathis Bessa |
| 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: | Server Serverless 2022-03-07, Server Serverless 2022-03-21 | ||||||||
| Participants: | |||||||||
| Description |
|
When a recipient primary steps up after a split, it will have a local out-of-date state document for the split which it originates from. When the recipient starts an instance for this state document and observes that the state is kBlocking and the local set name is equal to the stored recipientSetName, then the recipient should abort the current operation and delete the state document. We should make sure that this method is written generically to support additional cleanup if needed. |
| Comments |
| Comment by Githook User [ 09/Mar/22 ] |
|
Author: {'name': 'mathisbessamdb', 'email': 'mathis.bessa@mongodb.com', 'username': 'mathisbessamdb'}Message: |