Details
-
Bug
-
Status: Closed (View Workflow)
-
Blocker
-
Resolution: Fixed
-
10.1.10, 10.1.11, 10.1.12
-
None
-
# cat /etc/debian_version
8.3
# uname -a
Linux j285499.servers.jiffybox.net 4.1.16-x86_64-jb1 #1 SMP Wed Jan 27 07:37:00 CET 2016 x86_64 GNU/Linux
--
MariaDB [(none)]> select version();
+------------------------------+
| version() |
+------------------------------+
| 10.1.11-MariaDB-1~jessie-log |
+------------------------------+
1 row in set (0.00 sec)
MariaDB [(none)]># cat /etc/debian_version 8.3 # uname -a Linux j285499.servers.jiffybox.net 4.1.16-x86_64-jb1 #1 SMP Wed Jan 27 07:37:00 CET 2016 x86_64 GNU/Linux -- MariaDB [(none)]> select version(); +------------------------------+ | version() | +------------------------------+ | 10.1.11-MariaDB-1~jessie-log | +------------------------------+ 1 row in set (0.00 sec) MariaDB [(none)]>
Description
Two Galera Cluster with 3 nodes. Node 1 of each cluster is connected as master / master Async Replication.
The cluster crashes every time direct after a table has been created and a few insert and updates Statements.
Usually the table is lost on a cluster.
If a start only start Node 1 from each Cluster without WSREP_PROVIDER it works fine.
