Details
-
Task
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
None
Description
Galera 25.3.23 changed an internal RecordSet version number. This means that when you perform a rolling upgrade and your cluster contains nodes running mixed versions, where some are running Galera >= 25.3.23, and others are running Galera < 25.3.23, you can run into errors like this:
2019-03-15 14:59:53 139767287109376 [Note] WSREP: Shifting PRIMARY -> JOINER (TO: 87)
|
2019-03-15 14:59:53 139767614987008 [Note] WSREP: Requesting state transfer: success, donor: 0
|
2019-03-15 14:59:53 139767614987008 [Note] WSREP: GCache history reset: old(c0e116a0-466e-11e9-9991-ba2929288000:0) -> new(c0e116a0-466e-11e9-9991-ba2929288000:87)
|
2019-03-15 14:59:53 139767270323968 [ERROR] WSREP: Writeset deserialization failed: Unsupported RecordSet version: 2: 71 (Protocol error)
|
at galerautils/src/gu_rset.cpp:header_version():272
|
at galera/src/trx_handle.cpp:unserialize():268
|
WS flags: 0
|
Trx proto: 3
|
Trx source: 00000000-0000-0000-0000-000000000000
|
Trx conn_id: 18446744073709551615
|
Trx trx_id: 18446744073709551615
|
Trx last_seen: -1
|
2019-03-15 14:59:53 139767270323968 [ERROR] WSREP: got exception while reading ist stream: Unsupported RecordSet version: 2: 71 (Protocol error)
|
at galerautils/src/gu_rset.cpp:header_version():272
|
at galera/src/trx_handle.cpp:unserialize():268
|
2019-03-15 14:59:53 139767270323968 [ERROR] WSREP: IST didn't contain all write sets, expected last: 87 last received: 85
|
We should probably document this somewhere. Should this be in the release notes?
It looks like Galera 25.3.23 was first added in MariaDB 10.1.32 and 10.2.13:
https://mariadb.com/kb/en/library/mariadb-10132-release-notes/
https://mariadb.com/kb/en/library/mariadb-10213-release-notes/
It looks like MariaDB 10.3 was still in RC when Galera 25.3.23 was released, so we probably don't have to worry about documenting anything for that:
https://mariadb.com/kb/en/library/mariadb-1035-release-notes/