[SERVER-45087] Check Oplog Commitment condition on reconfig Created: 12/Dec/19 Updated: 29/Oct/23 Resolved: 26/Feb/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.4 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Siyuan Zhou | Assignee: | William Schultz (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | safe-reconfig-cmd | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||
| Sprint: | Repl 2020-02-10, Repl 2020-02-24, Repl 2020-03-09 | ||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||
| Linked BF Score: | 28 | ||||||||||||||||||||||||
| Description |
|
Oplog Commitment condition checks all committed entries in the previous config C_i-1 are also committed in the current config C_i. Skip oplog commitment check on force reconfig. |
| Comments |
| Comment by Siyuan Zhou [ 17/Apr/20 ] |
|
The waiting behavior of this ticket has been superseded by |
| Comment by Githook User [ 28/Feb/20 ] |
|
Author: {'name': 'William Schultz', 'username': 'will62794', 'email': 'william.schultz@mongodb.com'}Message: |
| Comment by Githook User [ 27/Feb/20 ] |
|
Author: {'username': 'will62794', 'name': 'William Schultz', 'email': 'william.schultz@mongodb.com'}Message: |
| Comment by Githook User [ 27/Feb/20 ] |
|
Author: {'name': 'William Schultz', 'username': 'will62794', 'email': 'william.schultz@mongodb.com'}Message: |
| Comment by Githook User [ 27/Feb/20 ] |
|
Author: {'username': 'will62794', 'name': 'William Schultz', 'email': 'william.schultz@mongodb.com'}Message: |
| Comment by Githook User [ 26/Feb/20 ] |
|
Author: {'username': 'will62794', 'name': 'William Schultz', 'email': 'william.schultz@mongodb.com'}Message: create mode 100644 jstests/replsets/reconfig_waits_for_oplog_commitment_condition.js |
| Comment by Siyuan Zhou [ 16/Dec/19 ] |
|
As daniel.hatcher suggested, we need to return the detailed reasons when a safe reconfig fails. When a safe reconfig succeeds, we should log that it's committed. |