Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

2025 Q1 maintaince release #634

Merged
merged 20 commits into from
Feb 5, 2025
Merged

2025 Q1 maintaince release #634

merged 20 commits into from
Feb 5, 2025

Conversation

grooverdan
Copy link
Member

No description provided.

START REPLIA was issued during initializing which mean that
even before /docker-entrypoint/initdb.d there was initializtion
going on.

Entrypoints that needed data initialzation didn't complete with
this nicely. Also if there wasn't any initialization there
would be little time for the replication to acheive anything
before being shutdown ready for the final start.

Moved --skip-slave-start to the default docker_temp_server_start
implementation.

Technically this is a compaibility break that is likely to be
of significants if:
* /docker-entrypoint/initdb.d contains a script waiting
  for replication to catch up.

The recitifcation to the previous behaviour is:
/docker-entrypoint/initdb.d contains a SQL to START REPLICA.
Recommend also having another script that is:

until healthcheck.sh --replication_io \
                     --replication_sql \
                     --replication_seconds_behind_master=0 \
                     --replication
                     --no-connect;
do
  sleep 1
done

Closes #614
There is an implicit --connect option in healthcheck
so that a normal use can be sure MariaDB is running
on a tcp socket.

There is a case in /docker-entrypoint-initdb.d where
its desirable to perform healthchecks for components
without a --connect. In this case, use --no-connect
in the healthcheck to avoid an implicit --connect test.
As highlighted in #630 a healthcheck.sh --mariadbuprade test
will use flock that is provided by util-linux-core on ubi systems.
For 10.5, 10.6, 10.11 and 11.4
@grooverdan
Copy link
Member Author

still needs version bumps from API

10.5.28, 10.6.21, 10.11.11, and 11.4.5 releases ...

10.5.28, 10.6.21, 10.11.11, and 11.4.5 releases
@grooverdan grooverdan merged commit 3bfeae4 into master Feb 5, 2025
13 checks passed
@grooverdan grooverdan deleted the next branch February 5, 2025 21:18
@grooverdan grooverdan restored the next branch February 5, 2025 23:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

1 participant