[MDEV-18944] Document rolling upgrade issues related to "Unsupported RecordSet version: 2" Created: 2019-03-15  Updated: 2019-03-22  Resolved: 2019-03-22

Status: Closed
Project: MariaDB Server
Component/s: Documentation - Support, Galera
Fix Version/s: N/A

Type: Task Priority: Major
Reporter: Geoff Montee (Inactive) Assignee: Kenneth Dyer (Inactive)
Resolution: Fixed Votes: 0
Labels: 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/

 Comments   
Comment by Geoff Montee (Inactive) [ 2019-03-20 ]

I added the following note:

Note that when upgrading the Galera wsrep provider, sometimes the Galera protocol version can change. The Galera wsrep provider should not start using the new protocol version until all cluster nodes have been upgraded to the new version, so this is not generally an issue during a rolling upgrade. However, this can cause issues if you restart a non-upgraded node in a cluster where the rest of the nodes have been upgraded.

https://mariadb.com/kb/en/library/upgrading-between-minor-versions-with-galera-cluster/

Generated at Thu Feb 08 08:47:54 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.