Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 5.5.35-galera
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
Description
Here is an example: https://mariadb.atlassian.net/browse/MDEV-5691
Its closed as not a bug so I thought I'd post a new bug about how problems like these can be better handled in the future.
If there is incompatibilities which will kick in place if you keep default/current config of galera/mariadb it should be specified in the changelog/announcement.
Now it was an issue with:
> It might happen because of mismatch in checksum algorithms being used at different nodes. 5.5.34 uses
> galera-2 (25.2.xx) which has socket.checksum=1, while 5.5.35 uses galera-3 (25.3.xx) where default
But I dont want this bug to be closed and not considered, if you read the above issue it seems like it was not properly tested before release? Could this be automated somehow?
Right now I wont add MariaDB's repo on production environments, there has been almost a breakage of every major release and the changelog has not documented these. so I have to file a bug of something that I feel should have been known/documented before release.
Please dont take this the wrong way I just want to be able to trust the repo enough to use it in production.
Thanks for an otherwise great product.
Gliffy Diagrams
Attachments
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions
An issue has been opened with Galera :
https://bugs.launchpad.net/galera/+bug/1285656
Hi Stefan,
We are making sure the incompatibilities (like this) get documented
in the release notes. Thanks again for the constructive feedback.
Make sure that incompatibilities between the releases are announced properly.
Hi Stefan,
Thanks for the feedback. I have added a note in the release notes stating this backward
incompatibility.