Details
-
Bug
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
10.4(EOL), 10.5, 10.6, 10.7(EOL), 10.8(EOL)
-
None
Description
Set to 10.4+ because I was looking at galera-4 and don't know whether galera[-3] has the same problem
Linux distributions, e.g. Ubuntu, provide their own galera-4 package. For example, in Ubuntu 20.04 Focal it's currently
Version: 26.4.3-4
|
Priority: optional
|
Section: universe/libs
|
Origin: Ubuntu
|
Maintainer: Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
|
When MariaDB server gets installed, it requires galera-4 as a dependency, but doesn't require any specific minor version of it. So, If the library like above is already installed, it won't be upgraded to the one from MariaDB repositories upon server installation.
However, the server doesn't seem to work very well with the library, at least MTR tests fail in different ways suggesting it might be not necessarily test-only issues. For example,
10.8.2 |
galera.galera_log_bin_opt 'innodb' [ fail ] Found warnings/errors in server log file!
|
Test ended at 2022-02-25 17:04:14
|
line
|
2022-02-25 17:04:08 0 [ERROR] WSREP: sst sent called when not SST donor, state JOINED
|
2022-02-25 17:04:08 0 [Warning] WSREP: wsrep::sst_sent() returned an error: Not connected to Primary Component
|
^ Found warnings in /dev/shm/var/log/mysqld.1.err
|
(There are other kinds of failures, not just this one).
We can't control the version of the library provided by the distributions; so, if the failures turn out to be real and the server really cannot work with certain libraries, something needs to be done at the packaging level – e.g. demand a certain minimal version, – to force the library to get upgraded to match the server.
Attachments
Issue Links
- relates to
-
MDEV-34575 galera.galera_var_wsrep_provider_options segfault with provider 26.4.16
- Open