Add replication journal cleanup when drop database #8626
+54
−13
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.
Problem: when deleting a DB, log segment files remain, which break replication in the future
First fix - when deleting a DB using DBMS query (drop database), add deleting segments
2.1. Execute the
drop database
command2.2. Restore via gbak with the
-recreate_database overwrite
or-replace_database
option, without deleting the DB and without clearing the journal directorySecond fix - add a unique GUID of the DB to the segment filename pattern