Problems using GTID replication a -> b(more info) -> c
I have an issue in a replication setup which from time-to-time stops
working. The customer is using GTID.
server-a is master
server-b replicates from server-a and adds its own data
server-c replicates from server-b and should have role as backup/standby
Sometimes it seems that server-c tries to connect to server-a, and not
to server-b as it should.
It might be related to some confusion about the received GTID
From server-c: SHOW SLAVE STATUS\G
...
Retrieved_Gtid_Set:
7213a549-c19d-11e4-b6b8-00505697a71e:205335827-1013317200,
cf7877d6-c19d-11e4-b6bb-00505697ac59:21509-232465
Executed_Gtid_Set:
7213a549-c19d-11e4-b6b8-00505697a71e:1-1013317200,
cf7877d6-c19d-11e4-b6bb-00505697ac59:1-232465,
fbdfd9ec-0937-11e5-89a3-00505697fdb5:1-645
there seems to be two sets received, and this may confuse replication of
server-c
When using the standard type of MySQL-replication, this type of adding
data in the middle slave/master works ok.
Truls Bergskaug
Subject
Views
Written By
Posted
Problems using GTID replication a -> b(more info) -> c
1281
October 08, 2015 08:04AM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.