Skip to content

fix(database-ha): improve startup and replication logging - #23

Merged
wanghe-fit2cloud merged 1 commit into
devfrom
fix/database-cluster-startup-logs
Nov 18, 2026
Merged

wanghe-fit2cloud merged 1 commit into
devfrom
fix/database-cluster-startup-logs

Conversation

@wanghe-fit2cloud

Copy link
Copy Markdown
Member

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:

  • Complete ARM64 native checks: MySQL 8.4.13, PostgreSQL 15.20/16.16/17.12/18.7, and Redis 6.2.24/7.4.12/8.10.3.
  • Complete AMD64 QEMU checks: MySQL 8.4.13, PostgreSQL 18.7, and Redis 8.10.3.
  • Passed 26 MySQL log fixtures, targeted PostgreSQL/Redis authentication and custom-log routing checks, Bash syntax, ShellCheck, and diff checks.

@wanghe-fit2cloud
wanghe-fit2cloud merged commit ed25eb3 into dev Nov 18, 2026
19 checks passed
@wanghe-fit2cloud
wanghe-fit2cloud deleted the fix/database-cluster-startup-logs branch November 18, 2026 03:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant