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

Galera Changes and MaxScale Removal #256

Merged
merged 3 commits into from
May 10, 2024
Merged

Conversation

LukeRepko
Copy link
Contributor

Maxscale was introduced to help thwart DBDeadlocks but it did not resolve that issue.

@the2hill
Copy link
Contributor

LGTM

LukeRepko added 3 commits May 10, 2024 14:13
It was introduced to help thwart DBDeadlocks but it did not help resolve
that issue.
Many recovery issues have been observed when losing a node during chaos
testing. Moving to a 5 node cluster has improved recovery success rate.
These changes were proposed by one of our DBAs to help cope with
DBDeadlocks. They seem to have helped reduce occurrences.
@LukeRepko LukeRepko merged commit c71badd into rackerlabs:main May 10, 2024
24 checks passed
@LukeRepko LukeRepko deleted the galera branch May 10, 2024 19:18
cloudnull pushed a commit that referenced this pull request Jun 19, 2024
* fix: Remove MaxScale

It was introduced to help thwart DBDeadlocks but it did not help resolve
that issue.

* fix: Make 5 replicas the default

Many recovery issues have been observed when losing a node during chaos
testing. Moving to a 5 node cluster has improved recovery success rate.

* fix: Improve galera performance

These changes were proposed by one of our DBAs to help cope with
DBDeadlocks. They seem to have helped reduce occurrences.
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.

2 participants