# Sync\_binlog=0 on master and orchestrator slave relocate issue

**URL:** <https://forums.percona.com/t/sync-binlog-0-on-master-and-orchestrator-slave-relocate-issue/30853>\
**Category:** MySQL & MariaDB\
**Tags:** mysql, percona\
**Created:** [June 6, 2024, 3:36pm UTC](https://forums.percona.com/t/sync-binlog-0-on-master-and-orchestrator-slave-relocate-issue/30853 "2024-06-06T15:36:54Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Dario\_Rigolin](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/dario_rigolin/32/16798_2.png) [@Dario\_Rigolin](https://forums.percona.com/u/Dario_Rigolin)\
**Post date:** [June 6, 2024, 3:36pm UTC](https://forums.percona.com/t/sync-binlog-0-on-master-and-orchestrator-slave-relocate-issue/30853/1 "2024-06-06T15:36:54Z")

</div>

I have a primary P with sync\_binlog=0 and 2 replicas R1 and R2 with sync\_binlog=1. Topology is P-\>R1-\>R2. I use orchestrator to monitor those servers. If I try to relocate R2 under P to have a topology P-\>(R2,R1) I receive an error where Orchestrator find different events on the P and R2 binary log. I’m using Automatic Pseudo GTID, and I presume that sync\_binlog=0 on master is not committing all on binary logs and this is the reason of the error in relocation. Did anybody had same issue before?

---

<div class="post-metadata">

**Author:** ![Mughees\_Ahmed](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/mughees_ahmed/32/9028_2.png) [@Mughees\_Ahmed](https://forums.percona.com/u/Mughees_Ahmed)\
**Post date:** [June 8, 2024, 7:38am UTC](https://forums.percona.com/t/sync-binlog-0-on-master-and-orchestrator-slave-relocate-issue/30853/2 "2024-06-08T07:38:50Z")

</div>

hello @Dario_Rigolin ,

Please share logs of orcheastrator and errors you get during the failover process. It helps to understand the issue by checking at the logs. thanks

---

<div class="post-metadata">

**Author:** ![Dario\_Rigolin](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/dario_rigolin/32/16798_2.png) [@Dario\_Rigolin](https://forums.percona.com/u/Dario_Rigolin)\
**Post date:** [June 10, 2024, 8:19am UTC](https://forums.percona.com/t/sync-binlog-0-on-master-and-orchestrator-slave-relocate-issue/30853/3 "2024-06-10T08:19:43Z")

</div>

Hi I have found the issue. Pseudo GTD want mandatory sync\_binlog=1, after changing this slave migration went well. Following documentation of Orchestrator sync\_binlog=1 and replication\_commit\_order need to be set to guaranteed same order of events on all slaves and I presume also on master. we have also some myisam tables on some databases and we are using MIXED binlog format. Sometimes MYISAM operation requires more time and this will increase lag on slaves. Moving from MyISAM to INNODB on bigger tables helped.

From my understanding of the replication process, master can work in parallel on many different database at same time and commit many transactions, instead replicas has to execute events in order and cannot work in parallel if we want to maintain same bin\_log events on all replicas.  
If we relax sync\_binlog and replication\_commit\_order replicas can work lot faster but orchestrator will not be able to relocate replicas.