Bug #113337 | Cluster View Inconsistent - New Primary Unable to be Promoted | ||
---|---|---|---|
Submitted: | 5 Dec 2023 10:29 | Modified: | 14 Jan 2024 11:37 |
Reporter: | Sameer Gavaskar | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | MySQL Operator | Severity: | S4 (Feature request) |
Version: | 8.2.0-2.1.1 | OS: | Linux (Amazon Linux 2) |
Assigned to: | CPU Architecture: | x86 (x86_64) |
[5 Dec 2023 10:29]
Sameer Gavaskar
[12 Dec 2023 14:21]
MySQL Verification Team
Hi, I could not reproduce this but I understand what happened to you and I do not believe this to be a bug. Any decent database system needs to favor consistency to anything else. Your request to have a config that can change this behavior could be taken in as feature request if that is ok with you but I cannot promise that our dev team will agree. If you want me to take this bug report as a feature request let us know. Thanks for using MySQL
[18 Dec 2023 21:37]
Simon Mudd
"Any decent database system needs to favor consistency to anything else." Slightly off-topic but I do not always agree with that. If you take down the database you can provide no service. That means an outage. If you choose to not take down an inconsistent database setup then you have chosen to accept the inconsistencies and resolve them (somehow) while the system is still up. That MAY trigger more problems but it does mean that to a percentage of your users/customers the service appears to be working and possibly the impact of the inconsistencies may not affect them. So in a technically pure database environment I would agree. However, in a business environment it may be better to have a partially working system than no system working at all. That decision can not be made by software but must be made by humans, those that operate the system in question. MySQL has traditionally been sufficiently flexible that it might trigger inconsistencies, the reason for GR helping to avoid "lost updates" or "split brains". Clearly we never want this to happen but if something does break having more flexibility in handling such issues is important. So I think the comment from the original poster was to have more flexibility in the configured setup. Real life is just more complex that we'd like.
[19 Dec 2023 10:12]
MySQL Verification Team
Hi Simon, Of course you are right and you have a system that demonstrate what you talk about perfectly. That is why I wrote "this behavior could be taken in as feature request if that is ok with you" as it would make sense as a FR. I still do not believe it is a bug, but I would accept it as FR.
[10 Jan 2024 16:25]
Sameer Gavaskar
Apologies for the late follow up here. Yes I think we would like to have this as a feature if possible.
[14 Jan 2024 11:37]
MySQL Verification Team
Thank you