diff options
| author | Daniele Sciascia <daniele.sciascia@galeracluster.com> | 2018-04-19 10:29:13 +0200 |
|---|---|---|
| committer | Daniele Sciascia <daniele.sciascia@galeracluster.com> | 2018-04-19 10:48:29 +0200 |
| commit | 3aa5f00e69343a44aa1eac599aed0117a5fa264c (patch) | |
| tree | aca964fac8af269c785f7b7d7af70e41a1ec3983 /sql/sql_class.h | |
| parent | 3d1ad2a5e85284b5ec4bb28f744b93b0b73e3934 (diff) | |
| download | mariadb-git-3aa5f00e69343a44aa1eac599aed0117a5fa264c.tar.gz | |
MDEV-15929 Fix lock wait timeout on `SELECT @@GLOBAL.WSREP_ON`
This patch fixes a lock wait timeout error on `SELECT @@GLOBAL.WSREP_ON`
in `wait_wsrep_ready.inc`:
```
--connection node_2
...
--source include/kill_galera.inc
--connection node_1
--source include/wait_until_connected_again.inc # This includes wait_wsrep_ready.inc
```
The problem is that on node_2, kill_galera.inc may return before
the node is killed. So node_1 may still see that node_1 is alive
and will attempt to sync wait when doing those `SELECT` statements.
But sync wait is doomed to fail given that node_1 is killed, hence
the lock wait timeout.
One possible fix is to disable wsrep_sync_wait before including
wait_until_connected_again.
However, it appears that including wait_until_connected_again is
not necessary at all in node_1, so this patch removes it altogether.
Diffstat (limited to 'sql/sql_class.h')
0 files changed, 0 insertions, 0 deletions
