Details
-
Task
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
Description
Steps:
1. Set up Galera cluster using branch 10.4 or 10.3 with 3 nodes.
2. Shutdown one node.
3. Upgrade the binaries used by that node to bb-10.4-galera4 and galera 4 library.
4. Start that server.
Expected: Upgraded node has joined the cluster.
5. Repeat the same for the rest of nodes.
Attachments
Issue Links
- relates to
-
MDEV-18407 Galera: Rolling upgrade: 10.3 nodes are stopped with signal 6 on attempt to join upgraded 10.4 node
-
- Closed
-
-
MDEV-18504 Galera 4: test manually bulk upgrade to Server 10.4 + Galera 4
-
- Closed
-
-
MDEV-18580 Galera: Rolling upgrade: Upgraded node 3 is stopped with signal 6 after node 2 shutdown
-
- Closed
-
-
MDEV-18629 Galera: Rolling upgrade: Upgraded node is stopped with signal 6 on attempt to join the cluster
-
- Closed
-
-
MDEV-18699 Galera: Rolling upgrade: Upgraded node is stopped on commit if wsrep_trx_fragment_size > 0
-
- Closed
-
-
MDEV-19983 Galera: Rolling upgrade: Upgraded node 2 cannot connect to the cluster on rows adding, updating, and removing during upgrade
-
- Closed
-
Status as of 27.02.2019.
The following scenarios have been tested:
1. PASSED: Without data loading during upgrade.
2. PASSED: Data loading during upgrade.
3. PASSED: Data updating and removing during upgrade.
4. FAILED: Schema changing during upgrade. Added a table and a column. Should be documented as a known limitation.
5. FAILED: Streaming replication on the partially upgraded cluster. See
MDEV-18699andMDEV-18552for it.6. Streaming replication on upgraded cluster. It worked for me, but shako has found an issue
MDEV-18631using sysbench.