# Show Slave Status - Impossible coordinates?

**URL:** <https://forums.percona.com/t/show-slave-status-impossible-coordinates/22707>\
**Category:** Percona Server for MySQL 5.7\
**Created:** [June 9, 2023, 3:56pm UTC](https://forums.percona.com/t/show-slave-status-impossible-coordinates/22707 "2023-06-09T15:56:18Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![ChrisDK](https://avatars.discourse-cdn.com/v4/letter/c/a6a055/32.png) [@ChrisDK](https://forums.percona.com/u/ChrisDK)\
**Post date:** [June 9, 2023, 3:56pm UTC](https://forums.percona.com/t/show-slave-status-impossible-coordinates/22707/1 "2023-06-09T15:56:19Z")

</div>

Recently I have a replication node that has errored. I noticed something that I think is impossible, but want to confirm:

The coordinates in the show slave status command seems impossible. Please note both IO and SQL threads are pointing to the same binary log file bin-1.084438. And yet the SQL thread coordinate is higher than the IO thread.

Master\_Log\_File: bin-1.084438  
Read\_Master\_Log\_Pos: 48870187  
Relay\_Master\_Log\_File: bin-1.084438  
Exec\_Master\_Log\_Pos: 765952106

The exec\_master\_log\_pos is a higher number than read\_master\_log\_pos within the same binary log file. I would think that exec\_master\_log\_pos can never be a higher number when in the same binary log file and at most can be the same number. Unless my logic is wrong it would seem at some point things got really messed up here and the sql thread somehow jumped ahead.

Any thoughts/comments would be appreciated. Perhaps my understanding of binary log position is not correct?

Thanks.

---

<div class="post-metadata">

**Author:** ![Ivan\_Groenewold](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/ivan_groenewold/32/6299_2.png) [@Ivan\_Groenewold](https://forums.percona.com/u/Ivan_Groenewold)\
**Post date:** [June 9, 2023, 4:27pm UTC](https://forums.percona.com/t/show-slave-status-impossible-coordinates/22707/2 "2023-06-09T16:27:04Z")

</div>

Hi, depending on your configuration, the metadata for each thread might be updated every few events (see for example [https://dev.mysql.com/doc/refman/8.0/en/replication-options-replica.html#sysvar\_sync\_master\_info](https://dev.mysql.com/doc/refman/8.0/en/replication-options-replica.html#sysvar_sync_master_info)) so I guess it is possible to see the IO thread behind the SQL thread. What is the error you are seeing exactly?

---

<div class="post-metadata">

**Author:** ![ChrisDK](https://avatars.discourse-cdn.com/v4/letter/c/a6a055/32.png) [@ChrisDK](https://forums.percona.com/u/ChrisDK)\
**Post date:** [June 9, 2023, 7:07pm UTC](https://forums.percona.com/t/show-slave-status-impossible-coordinates/22707/3 "2023-06-09T19:07:44Z")

</div>

I have another thread open regarding the error:

> [@Got fatal error 1236 from master when reading data from binary log](https://forums.percona.com/t/got-fatal-error-1236-from-master-when-reading-data-from-binary-log/22683/3):
>
> Did the replica crash recently ? One possibility is that the binary log entry is corrupted. Write down the file/pos for current replication, then forget replication settings (STOP SLAVE: RESET SLAVE ALL:) then set replication again to continue from where it left of