[MDEV-18699] Galera: Rolling upgrade: Upgraded node is stopped on commit if wsrep_trx_fragment_size > 0 Created: 2019-02-22 Updated: 2019-07-09 Resolved: 2019-05-03 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Galera |
| Affects Version/s: | 10.4.3 |
| Fix Version/s: | 10.4.5 |
| Type: | Bug | Priority: | Critical |
| Reporter: | Stepan Patryshev (Inactive) | Assignee: | Seppo Jaakola |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | galera, galera_4 | ||
| Environment: |
CentOS Linux release 7.6.1810 (Core) |
||
| Attachments: |
|
||||||||||||
| Issue Links: |
|
||||||||||||
| Description |
|
This issue was discovered on testing of Rolling Upgrade according to "MariaDB 10.4 Cluster Rolling Upgrade - Naive Approach" by Seppo Jaakola: https://docs.google.com/document/d/1z4XTpLpzStWMFaNnrSmiESaIVeCoKhu9Hbb1SrDPf0w 10.4.3-MariaDB-debug built from sources: commit f0b65102b23f006f596eef35e6e5f4f8b6d8146d Steps: 1. Start 3 MariaDB 10.3 nodes with mtr: 2. Copy [mysqld.3] group from var/my.cnf (attached my.cnf 2.1. Edit:
2.2. And add there also:
3.1 Load some data. 4. Upgrade node 3. 4.1 Stop the Server: 4.2. Make sure that wsrep-on is off: 4.3. Run 10.4 binaries with 10.3 data: 4.4. Run mysql_upgrade: 4.5. Stop the Server: 4.6. export PATH=$PATH:/home/stepan/mariadb/10.4/scripts 5. Check upgraded node 3 without the cluster. 5.1. Start the server: 5.2. Start the client: Actual result: 5.3. Stop the Server: 6. Join node 3 back to the cluster. 6.1. Add to /home/stepan/mariadb/10.3/mysql-test/var/mysqld.3.cnf:
6.2. Start the server: 7. Check how streaming replication behaves on partially upgraded cluster. 7.1. Run clients for all three nodes: /home/stepan/mariadb/10.3/client/mysql -u root -S /home/stepan/mariadb/10.3/mysql-test/var/tmp/mysqld.1.sock 7.2. Check with wsrep_trx_fragment_size by default. 7.2.1. On the Node 3:
Actual result: 7.2.2. On the Node 3:
Actual result: 7.3. Check with wsrep_trx_fragment_size > 0. 7.3.1. Set wsrep_trx_fragment_size > 0 on the Node 3:
7.3.2. On the Node 3:
Actual result: 7.3.3. On the Node 3:
Actual result: The node 3 has stopped: mysqld.3.err Expected result: Other log and config files are also attached. |
| Comments |
| Comment by Stepan Patryshev (Inactive) [ 2019-02-25 ] |
|
Here is the similar scenario: 1. Upgrade 2-nd and 3-rd nodes and join them to the cluster with the 1-st node which is still running on 10.3. 2. On the node 3: Actual result: And see also similar |
| Comment by Stepan Patryshev (Inactive) [ 2019-07-09 ] |
|
Confirm that it's fixed. Verified two scenarios on: MariaDB Server 10.4: branch 10.4, commit 9d6b601e797dd8333340dadaefae09ebafc787db. MariaDB Server 10.3: branch 10.3, commit 099007c3c92d1405625777fa86d2fba3da1d339c. |