[SERVER-35408] ReplicationCoordinatorExternalState and data replication must not be started after shutdown Created: 05/Jun/18 Updated: 06/Dec/22 Resolved: 05/Jun/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Matthew Russotto | Assignee: | Backlog - Replication Team |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Replication
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
It is possible for the ReplicationCoordinatorImpl to call startThreads on the ReplicationCoordinatorExternalState after calling shutdown() on the external state. In this case the ReplicationCoordinatorExternalState should refuse to start. Additionally, ReplicationCoordinatorImpl::_startDataReplication may be called after shutdown(). Further, if initial sync is required, ReplicationCoordinatorImpl::_startDataReplication should avoid creating the initial syncer after shutdown. |