Repository navigation
fix(database-ha): improve startup and replication logging - #23
Merged
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Database replication containers exposed too little startup progress to diagnose initialization failures. Route MySQL engine logs to container stdout and add timestamped stage logs for MySQL, PostgreSQL and Redis, including sanitized MySQL connection retry diagnostics. Preserve PostgreSQL and Redis custom logging destinations, and extend the existing checks to verify current-startup logs and keep configured test passwords out of output. MySQL readiness checks distinguish the final service from temporary initialization servers without depending on stdout/stderr ordering.
Local validation: