[SERVER-61376] Fix bugs related to FCBIS initial node becoming primary Created: 10/Nov/21 Updated: 29/Oct/23 Resolved: 11/Nov/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.2.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Matthew Russotto | Assignee: | Matthew Russotto |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Sprint: | Replication 2021-11-15 |
| Participants: |
| Description |
|
File copy based initial sync drops the local.replset.election (last vote) collection. While this is correct for backup because the node is subsequently restarted, for FCBIS we need to write a default last vote instead (for backup, that document is written when the node is restarted as a replica set) The JournalListener is reset when we restart storage. We need to restore it on the new storage engine or Replication will never advance its majority point as primary. |
| Comments |
| Comment by Githook User [ 11/Nov/21 ] |
|
Author: {'name': 'Matthew Russotto', 'email': 'matthew.russotto@mongodb.com', 'username': 'mtrussotto'}Message: |
| Comment by Githook User [ 11/Nov/21 ] |
|
Author: {'name': 'Matthew Russotto', 'email': 'matthew.russotto@mongodb.com', 'username': 'mtrussotto'}Message: |