This repository was archived by the owner on Feb 18, 2025. It is now read-only.
purge-binary-logs API, safe operation#825
Merged
shlomi-noach merged 1 commit intomasterfrom Mar 3, 2019
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Added
purge-binary-logs/:host/:port/:logFileAPI endpoint, supporting?force=truepurge-binary-logswill now refuse purging, by default, if the host has replicas which have not yet applied events in the binary logs to-be-purged.This is a strict sanity check. A more relaxed one would be to check if the replicas have copied the binary logs as relay logs. This is good enough on a normal flow, but since relay logs are purged on a
change master tocommand, they can lose their ability to replicas. Soorchestratorplays safe.