Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Not a Bug
-
10.3.35, 10.4.25
-
None
Description
A problem that supposedly was fixed (MDEV-22745, MDEV-20439, MDEV-22723, MDEV-19983) seems to still exist.
In this case the 10.4 node is replicating changes but still reporting:
wsrep_cluster_size as 0
wsrep_cluster_conf_id 18446744073709551615
The versions are:
On existing 2 nodes:
galera-25.3.35-1.el7.centos.x86_64
MariaDB-common-10.3.35-1.el7.centos.x86_64
MariaDB-server-10.3.35-1.el7.centos.x86_64
MariaDB-compat-10.3.35-1.el7.centos.x86_64
MariaDB-client-10.3.35-1.el7.centos.x86_64
MariaDB-backup-10.3.35-1.el7.centos.x86_64
MariaDB-shared-10.3.35-1.el7.centos.x86_64
On upgraded node:
galera-4-26.4.11-1.el7.centos.x86_64
MariaDB-compat-10.4.25-1.el7.centos.x86_64
MariaDB-server-10.4.25-1.el7.centos.x86_64
MariaDB-common-10.4.25-1.el7.centos.x86_64
MariaDB-backup-10.4.25-1.el7.centos.x86_64
MariaDB-client-10.4.25-1.el7.centos.x86_64
MariaDB-shared-10.4.25-1.el7.centos.x86_64
Tried a workaround also, starting with wsrep_on=OFF and turning it on afterwards, no luck (see attached)
Attachments
Issue Links
- relates to
-
MDEV-19983 Galera: Rolling upgrade: Upgraded node 2 cannot connect to the cluster on rows adding, updating, and removing during upgrade
- Closed
-
MDEV-20439 WSREP_CLUSTER_SIZE at 0 after rolling update a node
- Closed
-
MDEV-22723 Data loss when performing rolling upgrade from 10.3.23-MariaDB to 10.4.13-MariaDB
- Closed
-
MDEV-22745 node crash on upgrade from 10.3 to 10.4 writing on the 10.4 node
- Closed