Skip to content

Add a MariaDB recovery page - #1094

Draft
ideaship wants to merge 1 commit into
mainfrom
docs/mariadb-recovery
Draft

ideaship wants to merge 1 commit into
mainfrom
docs/mariadb-recovery

Conversation

@ideaship

Copy link
Copy Markdown
Contributor

Gives bringing back a MariaDB/Galera cluster that stopped completely, for example after a power outage, its own page in the operations guide. The Recovery subsection in infrastructure.md becomes a pointer to it.

What the page covers

  • Before you start — the MariaDB hosts and their count from osism get hosts -l mariadb, and database_password from osism vault view.
  • Recover the cluster — osism apply mariadb-recovery, which starts the cluster from the member with the highest Galera sequence number and joins the others to it.
  • Verify — wsrep status queried on every node directly, compared against the inventory count rather than what a running node reports, followed by OpenStack reads and a network create and delete from the manager.

The page stands on its own. Recovery is a routine operation, not part of restoring a backup, so it is kept apart from the MariaDB backup and restore guide:

The two PRs touch separate parts of infrastructure.md and merge cleanly in either order.

🤖 Generated with Claude Code

infrastructure.md covered bringing back a MariaDB/Galera cluster that
had stopped completely in two sentences and one command, with no word
on what to have ready or how to tell that the recovery worked.

Give it its own page under the operations guide. It lists what to
gather first on the manager, the MariaDB hosts and their count from
osism get hosts and database_password from osism vault view, then runs
osism apply mariadb-recovery and verifies the result. The check queries
wsrep status on every node directly rather than through the load
balancer and compares the cluster size against the inventory count, not
against what a running node reports, since API success alone cannot
detect a separate single-member Primary. It ends with OpenStack reads
and a network create and delete from the manager.

This is a routine operation, for example after a power outage, not part
of restoring a backup, so the page stands on its own rather than
sitting in the backup and restore material. The Recovery subsection in
infrastructure.md becomes a pointer to it.

Assisted-by: Claude:claude-opus-5-5
Signed-off-by: Roger Luethi <luethi@osism.tech>
@github-actions

Copy link
Copy Markdown

✅MegaLinter analysis: Success

Descriptor Linter Files Fixed Errors Max errors Warnings Elapsed time
✅ ACTION actionlint 5 0 0 0.05s
✅ JSON jsonlint 4 0 0 0.1s
✅ JSON prettier 4 0 0 0.36s
✅ JSON v8r 4 0 0 9.2s
✅ MARKDOWN markdownlint 172 0 0 3.48s
✅ MARKDOWN markdown-table-formatter 172 0 0 0.46s
✅ REPOSITORY betterleaks yes no no 0.91s
✅ REPOSITORY checkov yes no no 18.76s
✅ REPOSITORY git_diff yes no no 0.11s
✅ REPOSITORY secretlint yes no no 1.59s
✅ REPOSITORY trufflehog yes no no 4.24s
✅ SPELL codespell 182 0 0 0.79s
✅ SPELL lychee 182 0 0 16.88s
✅ YAML prettier 6 0 0 0.62s
✅ YAML v8r 6 0 0 7.7s
✅ YAML yamllint 6 0 0 0.59s

See detailed reports in MegaLinter artifacts

Your project could benefit from a custom flavor, which would allow you to run only the linters you need, and thus improve runtime performances. (Skip this info by defining FLAVOR_SUGGESTIONS: false)

  • Documentation: Custom Flavors
  • Command: npx mega-linter-runner@10.1.0 --custom-flavor-setup --custom-flavor-linters ACTION_ACTIONLINT,JSON_JSONLINT,JSON_V8R,JSON_PRETTIER,MARKDOWN_MARKDOWNLINT,MARKDOWN_MARKDOWN_TABLE_FORMATTER,REPOSITORY_CHECKOV,REPOSITORY_GIT_DIFF,REPOSITORY_BETTERLEAKS,REPOSITORY_SECRETLINT,REPOSITORY_TRUFFLEHOG,SPELL_LYCHEE,SPELL_CODESPELL,YAML_PRETTIER,YAML_YAMLLINT,YAML_V8R

MegaLinter is provided by OX Security
Show us your support by starring ⭐ the repository

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: New

Development

Successfully merging this pull request may close these issues.

2 participants