Skip to content

Delay to discard cached master when full synchronization#9398

Merged
oranagra merged 4 commits intoredis:unstablefrom
ShooterIT:delay-cache-master
Sep 9, 2021
Merged

Delay to discard cached master when full synchronization#9398
oranagra merged 4 commits intoredis:unstablefrom
ShooterIT:delay-cache-master

Conversation

@ShooterIT
Copy link
Member

Currently, once replica need to start full synchronization with master, it will discard cached master whatever full synchronization is failed or not. I think the cached master still is valid if failing to full synchronization, since replica's data is not changed during waiting data snapshot from master. Now we discard cached master only when transferring RDB is finished and start to change data space, this make replica could start partial resynchronization with another new master if new master is failed during full synchronization.

@enjoy-binbin
Copy link
Contributor

cool. I had the exact same idea before
when i debug the psync test

@oranagra oranagra added the state:to-be-merged The PR should be merged soon, even if not yet ready, this is used so that it won't be forgotten label Aug 20, 2021
@oranagra oranagra added the release-notes indication that this issue needs to be mentioned in the release notes label Aug 29, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approval-needed Waiting for core team approval to be merged release-notes indication that this issue needs to be mentioned in the release notes state:to-be-merged The PR should be merged soon, even if not yet ready, this is used so that it won't be forgotten

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

3 participants