[SERVER-57214] Add option of waiting for newlyAdded field removal in ReplSetTest Created: 26/May/21 Updated: 29/Oct/23 Resolved: 21/Jun/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.1.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Xuerui Fa | Assignee: | Xuerui Fa |
| 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: | Repl 2021-06-28 | ||||
| Participants: | |||||
| Linked BF Score: | 151 | ||||
| Description |
|
In the reInitiate() function of ReplSetTest, we currently do not wait for newlyAdded field to be removed. Callers of this function may only want to add a new node and wait for it to become a voter or electable, so we could consider adding the option to automatically wait for the newlyAdded field to be removed. We could also consider adding it to awaitSecondaryNodes() or awaitReplication(). We can probably call waitForAllNewlyAddedRemovals to accomplish this. |
| Comments |
| Comment by Vivian Ge (Inactive) [ 06/Oct/21 ] |
|
Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you! |
| Comment by Githook User [ 21/Jun/21 ] |
|
Author: {'name': 'XueruiFa', 'email': 'xuerui.fa@mongodb.com', 'username': 'XueruiFa'}Message: |
| Comment by Githook User [ 07/Jun/21 ] |
|
Author: {'name': 'XueruiFa', 'email': 'xuerui.fa@mongodb.com', 'username': 'XueruiFa'}Message: Revert " This reverts commit 3ac8fea75941c4041b877777997dee5e5c9847c0. |
| Comment by Githook User [ 07/Jun/21 ] |
|
Author: {'name': 'XueruiFa', 'email': 'xuerui.fa@mongodb.com', 'username': 'XueruiFa'}Message: |