DB migration #648
Open
DB migration #648
+748
−0
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
* Covered fresh install and Flyway adoption scenarios.
…, schema drift, baseline too low or too high, and concurrent startup.
vnandwana
commented
Feb 11, 2026
| * Duplicate migrations are skipped. | ||
|
|
||
|
|
||
| === Scenario 7 — Concurrent Startup (Multiple Aviate Nodes Running Migrations) |
Contributor
Author
There was a problem hiding this comment.
Spent some time testing this but couldn’t reproduce migration conflicts. Noticed that installing the Aviate plugin on one node automatically reflected on the other nodes and started successfully across all nodes.
Let me know if I need to spend more time on this (introduce startup delays, etc.) or this is sufficient for now.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Ticket -- https://github.com/killbill/killbill-aviate-plugin/issues/319
Documented all scenarios mentioned in the above ticket.