diff options
| author | mkaruza <mario.karuza@galeracluster.com> | 2021-08-18 10:13:02 +0200 |
|---|---|---|
| committer | Jan Lindström <jan.lindstrom@mariadb.com> | 2021-08-18 12:20:06 +0300 |
| commit | da171182b7d79d21177d113d2bbaecbca21d8bbc (patch) | |
| tree | 655ee4ddff352ee2c800bef6de094d8e3265e3c8 /sql/semisync_slave.cc | |
| parent | cce33787c37a6a0724e518f0f74a445a3682dfc4 (diff) | |
| download | mariadb-git-da171182b7d79d21177d113d2bbaecbca21d8bbc.tar.gz | |
MDEV-26223 Galera cluster node consider old server_id value even after modification of server_id [wsrep_gtid_mode=ON]bb-10.5-rasmus
If cluster is bootstrapped in existing database, we should use provided
configuration variables for wsrep_gtid_domain_id and server_id instead
of recovered ones.
If 'new' combination of wsrep_gtid_domain_id & server_id already existed
somewere before in binlog we should continue from last seqno, if
combination is new we start from seqno 0.
Reviewed-by: Jan Lindström <jan.lindstrom@mariadb.com>
Diffstat (limited to 'sql/semisync_slave.cc')
0 files changed, 0 insertions, 0 deletions