MDEV-36711 Galera Cluster node reports wrong error code in detached state #500
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
…tate Bug fix for a Galera Cluster bug: When a Galera Cluster node is detached from the cluster it may report wrong error code for an executed query. This caused the MTR test galera.MDEV-35946 for MDEV-35946.
|
Isn't this essentially the same as already submitted MariaDB#3975 ? |
|
Yes, it looks the same. |
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.
Bug fix for a Galera Cluster bug: When a Galera Cluster node is detached from the cluster it may report wrong error code for an executed query. This caused the MTR test galera.MDEV-35946 for MDEV-35946.
The problem occurs because the gategory of the table mysql.wsrep_streaming_log was changed from TABLE_CATEGORY_MYSQL to TABLE_CATEGORY_INFORMATION by the fix for MDEV-33881 Userstat skips system tables inconsistently. This is a new issue unrelated to the problem described by MDEV-35946.