tag:blogger.com,1999:blog-1135944569112521190.post7298555623189061144..comments2024-03-28T08:20:49.787+01:00Comments on Daniël's Database Blog: The importance of multi source replicationDaniël van Eedenhttp://www.blogger.com/profile/14757324605223498151noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-1135944569112521190.post-6856139675724962132014-05-23T09:59:12.211+02:002014-05-23T09:59:12.211+02:00That should be possible.That should be possible.Daniël van Eedenhttps://www.blogger.com/profile/14757324605223498151noreply@blogger.comtag:blogger.com,1999:blog-1135944569112521190.post-30815526799755406732014-05-22T18:21:00.738+02:002014-05-22T18:21:00.738+02:00I have 4 mater servers, will it be possible to ach...I have 4 mater servers, will it be possible to achieve multi master and multi- source replication at same time?In other words, replicating database from many to one and one to many at same time. Anonymoushttps://www.blogger.com/profile/10952235083683638941noreply@blogger.comtag:blogger.com,1999:blog-1135944569112521190.post-15602826894834463192013-11-25T08:08:53.329+01:002013-11-25T08:08:53.329+01:00For this test I was using "SHOW SLAVE STATUS ...For this test I was using "SHOW SLAVE STATUS FOR CHANNEL ='c1'", which for me seems to behave as expected. I wasn't using GTIDs. The RECEIVED_TRANSACTION_SET column in performance_schema.replication_connection_status remained empty. So this indeed P_S monitoring seems to require GTIDs.<br />mysql> SELECT * FROM performance_schema.replication_connection_status\G<br />*************************** 1. row ***************************<br /> CHANNEL_NAME: c1<br /> SOURCE_UUID: d65f823f-544b-11e3-a88a-f0def1356547<br /> THREAD_ID: 23<br /> SERVICE_STATE: ON<br />RECEIVED_TRANSACTION_SET: <br /> LAST_ERROR_NUMBER: 0<br /> LAST_ERROR_MESSAGE: <br /> LAST_ERROR_TIMESTAMP: 0000-00-00 00:00:00<br />*************************** 2. row ***************************<br /> CHANNEL_NAME: c2<br /> SOURCE_UUID: e0f99c98-544b-11e3-a88a-f0def1356547<br /> THREAD_ID: 25<br /> SERVICE_STATE: ON<br />RECEIVED_TRANSACTION_SET: <br /> LAST_ERROR_NUMBER: 0<br /> LAST_ERROR_MESSAGE: <br /> LAST_ERROR_TIMESTAMP: 0000-00-00 00:00:00<br />2 rows in set (0.01 sec)<br /><br />mysql> SELECT * FROM performance_schema.replication_execute_status\G<br />*************************** 1. row ***************************<br /> CHANNEL_NAME: c1<br /> SERVICE_STATE: ON<br />REMAINING_DELAY: NULL<br />*************************** 2. row ***************************<br /> CHANNEL_NAME: c2<br /> SERVICE_STATE: ON<br />REMAINING_DELAY: NULL<br />2 rows in set (0.00 sec)<br /><br />mysql> SELECT USER,COMMAND,STATE FROM information_schema.processlist ORDER BY STATE\G<br />*************************** 1. row ***************************<br /> USER: msandbox<br />COMMAND: Query<br /> STATE: executing<br />*************************** 2. row ***************************<br /> USER: rsandbox<br />COMMAND: Binlog Dump<br /> STATE: Master has sent all binlog to slave; waiting for binlog to be up<br />*************************** 3. row ***************************<br /> USER: rsandbox<br />COMMAND: Binlog Dump<br /> STATE: Master has sent all binlog to slave; waiting for binlog to be up<br />*************************** 4. row ***************************<br /> USER: system user<br />COMMAND: Connect<br /> STATE: Slave has read all relay log; waiting for the slave I/O thread t<br />*************************** 5. row ***************************<br /> USER: system user<br />COMMAND: Connect<br /> STATE: Slave has read all relay log; waiting for the slave I/O thread t<br />*************************** 6. row ***************************<br /> USER: system user<br />COMMAND: Connect<br /> STATE: Waiting for master to send event<br />*************************** 7. row ***************************<br /> USER: system user<br />COMMAND: Connect<br /> STATE: Waiting for master to send event<br />7 rows in set (0.01 sec)<br /><br /><br /><br /><br />Daniël van Eedenhttps://www.blogger.com/profile/14757324605223498151noreply@blogger.comtag:blogger.com,1999:blog-1135944569112521190.post-2716135340386494642013-11-24T19:45:14.904+01:002013-11-24T19:45:14.904+01:00Only theoretically you can skip log-slave-updates....Only theoretically you can skip log-slave-updates. Monitoring multi-source replication using P_S tables requires GTID, which in turn requires log-slave-updates.Giuseppe Maxiahttps://www.blogger.com/profile/15801583338057324813noreply@blogger.com