Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.4.2, 10.3.13
-
Ubuntu 18.04
Description
Hi, I used following scenario:
Tested on Ubuntu 18.04 desktop with -> 10.3.13-MariaDB-debug and 10.4.3-MariaDB-debug
• Start given number of nodes - with my test 5 nodes with 10.3 Maria + 3.x Galera.
• Stop node5
• start node5 with 10.4 Maria + 4.x Galera.
• Run mysqld_upgrade on node5
After that for not losing node5 with DDL as described here -> https://jira.mariadb.org/browse/MDEV-18422
I have created table on node5(10.4) as:
CREATE TABLE `sbtest4` ( |
`id` int(10) NOT NULL, |
PRIMARY KEY (`id`) |
) ENGINE=InnoDB DEFAULT CHARSET=latin1 |
It is successfully replicated to other nodes.
Then from node1:
CREATE TABLE IF NOT EXISTS temp4 AS (SELECT * FROM sbtest4); |
CREATE TABLE IF NOT EXISTS temp5 AS (SELECT * FROM sbtest4); |
insert into sbtest4(id) values(1); |
update sbtest4 set id=15 where id=1; |
From node5 error log:
2019-02-04 18:29:24 3 [Warning] WSREP: Could not find applier context for a72a266b-2888-11e9-8b7d-769edf8241a9: 43 |
2019-02-04 18:29:26 3 [Warning] WSREP: Could not find applier context for a72a266b-2888-11e9-8b7d-769edf8241a9: 51 |
2019-02-04 18:29:29 3 [Warning] WSREP: Could not find applier context for a72a266b-2888-11e9-8b7d-769edf8241a9: 59 |
2019-02-04 18:29:33 3 [Warning] WSREP: Could not find applier context for a72a266b-2888-11e9-8b7d-769edf8241a9: 67 |
2019-02-04 18:35:59 3 [Warning] WSREP: Could not find applier context for a72a266b-2888-11e9-8b7d-769edf8241a9: 68 |
2019-02-04 18:36:05 3 [Warning] WSREP: Could not find applier context for a72a266b-2888-11e9-8b7d-769edf8241a9: 70 |
2019-02-04 18:36:43 3 [Warning] WSREP: Could not find applier context for a72a266b-2888-11e9-8b7d-769edf8241a9: 76 |
2019-02-04 18:37:31 3 [Warning] WSREP: Could not find applier context for a72a266b-2888-11e9-8b7d-769edf8241a9: 86 |
2019-02-04 18:41:34 3 [Warning] WSREP: Could not find applier context for a72a266b-2888-11e9-8b7d-769edf8241a9: 92 |