{"id":2557,"date":"2021-08-19T13:12:49","date_gmt":"2021-08-19T13:12:49","guid":{"rendered":"http:\/\/kedar.nitty-witty.com\/?p=2557"},"modified":"2023-05-18T14:36:30","modified_gmt":"2023-05-18T14:36:30","slug":"relay-log-read-failure-2-many-dots-can-break-your-replication-only-once","status":"publish","type":"post","link":"https:\/\/kedar.nitty-witty.com\/blog\/relay-log-read-failure-2-many-dots-can-break-your-replication-only-once","title":{"rendered":"Relay log read failure | 2 many dots can break your replication only once"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Two or more dots in your relay log or binary log names can break replication; but worry not, it will only do it once. If you request to start again, it will work. That&#8217;s it, that&#8217;s the blog. Should you choose to spend some more time, go ahead.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><meta http-equiv=\"content-type\" content=\"text\/html; charset=utf-8\"><\/meta>Last_SQL_Error: Relay log read failure: Could not parse relay log event entry.<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A new MySQL 5.7 GTID replication chain was being constructed and fail-overs were being tested while an oddity of MySQL replication revealed itself. The Orchestrator graceful fail-over was not able to attach the replica and reporting an error.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Last_SQL_Error: Relay log read failure: Could not parse relay log event entry. The possible reasons are: the master's binary log is corrupted (you can check this by running 'mysqlbinlog' on the binary log), the slave's relay log is corrupted (you can check this by running 'mysqlbinlog' on the relay log), a network problem, or a bug in the master's or slave's MySQL code. If you want to check the master's binary log or slave's relay log, you will be able to know their names by issuing 'SHOW SLAVE STATUS' on this slave.<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Every possibility was investigated:<\/p>\n\n\n\n<!--more-->\n\n\n\n<ul class=\"wp-block-list\">\n<li>&#8220;the master&#8217;s binary log is corrupted&#8221;: No, master binary logs were okay. The mysqlbinlog utility was able to correctly parse the binary logs.<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>&#8220;the slave&#8217;s relay log is corrupted&#8221;: No, replica&#8217;s binary logs were okay. The mysqlbinlog utility was able to correctly parse the binary logs.<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>&#8220;a network problem&#8221;: telnet on port, no packet drops, no firewalls and mainly replication was working before failover!<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">How the error was fixed:<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">START SLAVE. <\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Hit the start slave again! Yes, on that error if you hit &#8220;start slave&#8221;, it starts working like a good boy. <\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Observation<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">It was later noted that the relay-log name was not regular. The one with NAME-followed-by-DIGITS. Instead it was incomplete filename provided and no trailing digits. Sounds like a MySQL bug?<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This issue appeared on MySQL 5.7.35 and even a lower minor-version. It hasn&#8217;t been tested in MySQL 8 yet.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Reproducing MySQL Replication Error &#8211; relay-bin <\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">So, it was time to bring this creature to lab and have tests. Let&#8217;s go back to the setup and try to regenerate this. We have two MySQL 5.7 instances in GTID replication with following configuration:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>## mysql1 - my.cnf\n &#91;mysqld]\n server-id = 1\n binlog_format = MIXED\n log-bin\n sync_binlog = 1\n gtid-mode=ON\n enforce-gtid-consistency\n relay-log=this.is.relay.log\n\n## mysql2 - my.cnf\n &#91;mysqld]\n server-id = 2\n binlog_format = MIXED\n log-bin\n sync_binlog = 1\n gtid-mode=ON\n enforce-gtid-consistency\n relay-log=this.is.relay.log<\/code><\/pre>\n\n\n\n<pre class=\"wp-block-code\"><code># Once instances are up, setup replication\nchange master to master_host='mysql1', master_user='repl', master_password='X', master_auto_position=1;\nstart slave; \nshow slave status\\G<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\" id=\"block-aa620fa5-47f6-4305-ae7c-3e418663ff6c\">So what you observe is:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Last_SQL_Error: Relay log read failure: Could not parse relay log event entry. The possible reasons are: the master's binary log is corrupted (you can check this by running 'mysqlbinlog' on the binary log), the slave's relay log is corrupted (you can check this by running 'mysqlbinlog' on the relay log), a network problem, or a bug in the master's or slave's MySQL code. If you want to check the master's binary log or slave's relay log, you will be able to know their names by issuing 'SHOW SLAVE STATUS' on this slave.<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">(If you see no error first time, try <em>stop slave; start slave; show slave status<\/em>\\<em>G<\/em> again.)<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Now, if you attempt to START SLAVE again, it will work!!<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">My Worklog from local MySQL Setup<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>\nmysql&gt; change master to master_host='mysql1', master_user='repl', master_password='X', master_auto_position=1;\nQuery OK, 0 rows affected, 2 warnings (0.01 sec)\n\nmysql&gt; show slave status\\G\n*************************** 1. row ***************************\n               Slave_IO_State:\n                  Master_Host: mysql1\n                  Master_User: repl\n                  Master_Port: 3306\n                Connect_Retry: 60\n              Master_Log_File: 645d6e993851-bin.000001\n          Read_Master_Log_Pos: 2333\n               Relay_Log_File: this.is.relay\n                Relay_Log_Pos: 2754\n        Relay_Master_Log_File: 645d6e993851-bin.000001\n             Slave_IO_Running: No\n            Slave_SQL_Running: No\n              Replicate_Do_DB:\n          Replicate_Ignore_DB:\n           Replicate_Do_Table:\n       Replicate_Ignore_Table:\n      Replicate_Wild_Do_Table:\n  Replicate_Wild_Ignore_Table:\n                   Last_Errno: 0\n                   Last_Error:\n                 Skip_Counter: 0\n          Exec_Master_Log_Pos: 2333\n              Relay_Log_Space: 2754\n              Until_Condition: None\n               Until_Log_File:\n                Until_Log_Pos: 0\n           Master_SSL_Allowed: No\n           Master_SSL_CA_File:\n           Master_SSL_CA_Path:\n              Master_SSL_Cert:\n            Master_SSL_Cipher:\n               Master_SSL_Key:\n        Seconds_Behind_Master: NULL\nMaster_SSL_Verify_Server_Cert: No\n                Last_IO_Errno: 0\n                Last_IO_Error:\n               Last_SQL_Errno: 0\n               Last_SQL_Error:\n  Replicate_Ignore_Server_Ids:\n             Master_Server_Id: 1\n                  Master_UUID: 054d4ac0-0023-11ec-934c-0242ac130002\n             Master_Info_File: \/var\/lib\/mysql\/master.info\n                    SQL_Delay: 0\n          SQL_Remaining_Delay: NULL\n      Slave_SQL_Running_State:\n           Master_Retry_Count: 86400\n                  Master_Bind:\n      Last_IO_Error_Timestamp:\n     Last_SQL_Error_Timestamp:\n               Master_SSL_Crl:\n           Master_SSL_Crlpath:\n           Retrieved_Gtid_Set: 054d4ac0-0023-11ec-934c-0242ac130002:1-8\n            Executed_Gtid_Set: 054d4ac0-0023-11ec-934c-0242ac130002:1-8\n                Auto_Position: 1\n         Replicate_Rewrite_DB:\n                 Channel_Name:\n           Master_TLS_Version:\n1 row in set (0.00 sec)\n\nmysql&gt; start slave;\nQuery OK, 0 rows affected (0.01 sec)\n\nmysql&gt; show slave status\\G\n*************************** 1. row ***************************\n               Slave_IO_State: Waiting for master to send event\n                  Master_Host: mysql1\n                  Master_User: repl\n                  Master_Port: 3306\n                Connect_Retry: 60\n              Master_Log_File: 645d6e993851-bin.000001\n          Read_Master_Log_Pos: 3565\n               Relay_Log_File: this.is.relay\n                Relay_Log_Pos: 3161\n        Relay_Master_Log_File: 645d6e993851-bin.000001\n             Slave_IO_Running: Yes\n            Slave_SQL_Running: No\n              Replicate_Do_DB:\n          Replicate_Ignore_DB:\n           Replicate_Do_Table:\n       Replicate_Ignore_Table:\n      Replicate_Wild_Do_Table:\n  Replicate_Wild_Ignore_Table:\n                   Last_Errno: 1594\n                   Last_Error: Relay log read failure: Could not parse relay log event entry. The possible reasons are: the master's binary log is corrupted (you can check this by running 'mysqlbinlog' on the binary log), the slave's relay log is corrupted (you can check this by running 'mysqlbinlog' on the relay log), a network problem, or a bug in the master's or slave's MySQL code. If you want to check the master's binary log or slave's relay log, you will be able to know their names by issuing 'SHOW SLAVE STATUS' on this slave.\n                 Skip_Counter: 0\n          Exec_Master_Log_Pos: 123\n              Relay_Log_Space: 4501\n              Until_Condition: None\n               Until_Log_File:\n                Until_Log_Pos: 0\n           Master_SSL_Allowed: No\n           Master_SSL_CA_File:\n           Master_SSL_CA_Path:\n              Master_SSL_Cert:\n            Master_SSL_Cipher:\n               Master_SSL_Key:\n        Seconds_Behind_Master: NULL\nMaster_SSL_Verify_Server_Cert: No\n                Last_IO_Errno: 0\n                Last_IO_Error:\n               Last_SQL_Errno: 1594\n               Last_SQL_Error: Relay log read failure: Could not parse relay log event entry. The possible reasons are: the master's binary log is corrupted (you can check this by running 'mysqlbinlog' on the binary log), the slave's relay log is corrupted (you can check this by running 'mysqlbinlog' on the relay log), a network problem, or a bug in the master's or slave's MySQL code. If you want to check the master's binary log or slave's relay log, you will be able to know their names by issuing 'SHOW SLAVE STATUS' on this slave.\n  Replicate_Ignore_Server_Ids:\n             Master_Server_Id: 1\n                  Master_UUID: 054d4ac0-0023-11ec-934c-0242ac130002\n             Master_Info_File: \/var\/lib\/mysql\/master.info\n                    SQL_Delay: 0\n          SQL_Remaining_Delay: NULL\n      Slave_SQL_Running_State:\n           Master_Retry_Count: 86400\n                  Master_Bind:\n      Last_IO_Error_Timestamp:\n     Last_SQL_Error_Timestamp: 210818 17:18:04\n               Master_SSL_Crl:\n           Master_SSL_Crlpath:\n           Retrieved_Gtid_Set: 054d4ac0-0023-11ec-934c-0242ac130002:1-12\n            Executed_Gtid_Set: 054d4ac0-0023-11ec-934c-0242ac130002:1-8\n                Auto_Position: 1\n         Replicate_Rewrite_DB:\n                 Channel_Name:\n           Master_TLS_Version:\n1 row in set (0.00 sec)\n\nmysql&gt; start slave;\nQuery OK, 0 rows affected (0.00 sec)\n\nmysql&gt; show slave status\\G\n*************************** 1. row ***************************\n               Slave_IO_State: Waiting for master to send event\n                  Master_Host: mysql1\n                  Master_User: repl\n                  Master_Port: 3306\n                Connect_Retry: 60\n              Master_Log_File: 645d6e993851-bin.000001\n          Read_Master_Log_Pos: 3565\n               Relay_Log_File: this.is.relay\n                Relay_Log_Pos: 4501\n        Relay_Master_Log_File: 645d6e993851-bin.000001\n             Slave_IO_Running: Yes\n            Slave_SQL_Running: Yes\n              Replicate_Do_DB:\n          Replicate_Ignore_DB:\n           Replicate_Do_Table:\n       Replicate_Ignore_Table:\n      Replicate_Wild_Do_Table:\n  Replicate_Wild_Ignore_Table:\n                   Last_Errno: 0\n                   Last_Error:\n                 Skip_Counter: 0\n          Exec_Master_Log_Pos: 3565\n              Relay_Log_Space: 4501\n              Until_Condition: None\n               Until_Log_File:\n                Until_Log_Pos: 0\n           Master_SSL_Allowed: No\n           Master_SSL_CA_File:\n           Master_SSL_CA_Path:\n              Master_SSL_Cert:\n            Master_SSL_Cipher:\n               Master_SSL_Key:\n        Seconds_Behind_Master: 0\nMaster_SSL_Verify_Server_Cert: No\n                Last_IO_Errno: 0\n                Last_IO_Error:\n               Last_SQL_Errno: 0\n               Last_SQL_Error:\n  Replicate_Ignore_Server_Ids:\n             Master_Server_Id: 1\n                  Master_UUID: 054d4ac0-0023-11ec-934c-0242ac130002\n             Master_Info_File: \/var\/lib\/mysql\/master.info\n                    SQL_Delay: 0\n          SQL_Remaining_Delay: NULL\n      Slave_SQL_Running_State: Slave has read all relay log; waiting for more updates\n           Master_Retry_Count: 86400\n                  Master_Bind:\n      Last_IO_Error_Timestamp:\n     Last_SQL_Error_Timestamp:\n               Master_SSL_Crl:\n           Master_SSL_Crlpath:\n           Retrieved_Gtid_Set: 054d4ac0-0023-11ec-934c-0242ac130002:1-12\n            Executed_Gtid_Set: 054d4ac0-0023-11ec-934c-0242ac130002:1-12\n                Auto_Position: 1\n         Replicate_Rewrite_DB:\n                 Channel_Name:\n           Master_TLS_Version:\n1 row in set (0.00 sec)<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">It is possibly understood why it fails for the first time, may be due to trimmed relay-log name, but then why it works with on the consecutive attempt to <em>start slave<\/em>!<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The observation here is if you use DOT in the filename for relay-log, it is trimmed. The maximum dots it can tolerate is 1, though it trims the filename after that dot but it doesn&#8217;t break replication. This is really odd and I tried reviewing the code but didn&#8217;t get enough time to go through that completely, If you&#8217;re interested to <a href=\"https:\/\/github.com\/mysql\/mysql-server\/blob\/beb865a960b9a8a16cf999c323e46c5b0c67f21f\/sql\/sys_vars.cc.\" target=\"_blank\" rel=\"noreferrer noopener nofollow\">investigate<\/a>, please be my guest and don&#8217;t forget to comment.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Some  relay-log config experiments<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>Configuring: \"relay-log=this.is.relay.log\"<br>Creates: \"this.index\" and \"this.is.relay\"<br>Replication: breaks for first start-slave and works in the next.<\/code><\/pre>\n\n\n\n<pre class=\"wp-block-code\"><code>Configuring: \"relay-log=thisis.relay.log\"<br>Creates: \"thisis.index\" and \"thisis.relay\"<br>Replication: breaks for first start-slave and works in the next.<\/code><\/pre>\n\n\n\n<pre class=\"wp-block-code\"><code>Configuring: \"relay-log=thisisrelay.log\"<br>Creates: \"thisisrelay.index\" and \"thisisrelay.000001\"<br>Replication: OK<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\">Even log-bin hates DOTs<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Wait, if you think this is over, it is not. This DOT fun is not only limited to <strong>relay-log <\/strong>but also<strong> <\/strong>extends to<strong> log-bin<\/strong>.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Configuring: \"log-bin=this.is.bin.log\"\nCreates: \"this.is.bin\"!<\/code><\/pre>\n\n\n\n<pre class=\"wp-block-code\"><code>mysql&gt; show binary logs;<br>+---------------+-----------+<br>| Log_name | File_size |<br>+---------------+-----------+<br>| this.is.bin | 194 |<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Wonder how the next binary log will progress and what will happen once the max-binlog-size is reached! May be it will overwrite the same binlog&#8230; I decided stop having these experiments and to let the capable MySQL team to figure this out.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">I already have raised the MySQL <a href=\"https:\/\/bugs.mysql.com\/bug.php?id=104665\" target=\"_blank\" rel=\"noreferrer noopener nofollow\">bug report.<\/a> Cheers.<\/p>\n","protected":false},"excerpt":{"rendered":"Two or more dots in your relay log or binary log names can break replication; but worry not, it will only do it once. If you request to start again,&hellip;\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[8,377],"tags":[401,380,427,495,589,494,100],"class_list":["post-2557","post","type-post","status-publish","format-standard","category-mysql","category-mysql-articles","tag-binary-log","tag-gtid-replication","tag-mysql","tag-mysql-bug","tag-relay-log-read-failure","tag-relay-log","tag-replication"],"aioseo_notices":[],"aioseo_head":"\n\t\t<!-- All in One SEO 4.9.10 - aioseo.com -->\n\t<meta name=\"description\" content=\"Two or more dots in your relay log or binary log names can break replication; but worry not, it will only do it once. If you request to start again, it will work. That&#039;s it, that&#039;s the blog. Should you choose to spend some more time, go ahead. Last_SQL_Error: Relay log read failure: Could not Having two or more dots in your relay-log or log-bin configuration will break the replication once. This is the blog to anticipate on this bug I posted.\" \/>\n\t<meta name=\"robots\" content=\"max-image-preview:large\" \/>\n\t<meta name=\"author\" content=\"Kedar\"\/>\n\t<meta name=\"google-site-verification\" content=\"_Bu1h5r0PxIC0D2jBVdmYN45RTeG9ogcX85XLkbG1qA\" \/>\n\t<meta name=\"msvalidate.01\" content=\"116B62074CBCA1BA99B8CCE09CCF2FB8\" \/>\n\t<meta name=\"keywords\" content=\"binary log,gtid replication,mysql,mysql bug,relay log read failure,relay-log,replication\" \/>\n\t<link rel=\"canonical\" href=\"https:\/\/kedar.nitty-witty.com\/blog\/relay-log-read-failure-2-many-dots-can-break-your-replication-only-once\" \/>\n\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 4.9.10\" \/>\n\t\t<meta property=\"og:locale\" content=\"en_US\" \/>\n\t\t<meta property=\"og:site_name\" content=\"Change Is Inevitable | Kedar Vaijanapurkar&#039;s Blog for MySQL, technology and various subjects\" \/>\n\t\t<meta property=\"og:type\" content=\"article\" \/>\n\t\t<meta property=\"og:title\" content=\"Relay log read failure | 2 many dots can break your replication only once | Change Is Inevitable\" \/>\n\t\t<meta property=\"og:description\" content=\"Two or more dots in your relay log or binary log names can break replication; but worry not, it will only do it once. If you request to start again, it will work. That&#039;s it, that&#039;s the blog. Should you choose to spend some more time, go ahead. Last_SQL_Error: Relay log read failure: Could not Having two or more dots in your relay-log or log-bin configuration will break the replication once. This is the blog to anticipate on this bug I posted.\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/kedar.nitty-witty.com\/blog\/relay-log-read-failure-2-many-dots-can-break-your-replication-only-once\" \/>\n\t\t<meta property=\"article:published_time\" content=\"2021-08-19T13:12:49+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2023-05-18T14:36:30+00:00\" \/>\n\t\t<meta name=\"twitter:card\" content=\"summary\" \/>\n\t\t<meta name=\"twitter:title\" content=\"Relay log read failure | 2 many dots can break your replication only once | Change Is Inevitable\" \/>\n\t\t<meta name=\"twitter:description\" content=\"Two or more dots in your relay log or binary log names can break replication; but worry not, it will only do it once. If you request to start again, it will work. That&#039;s it, that&#039;s the blog. Should you choose to spend some more time, go ahead. Last_SQL_Error: Relay log read failure: Could not Having two or more dots in your relay-log or log-bin configuration will break the replication once. This is the blog to anticipate on this bug I posted.\" \/>\n\t\t<script type=\"application\/ld+json\" class=\"aioseo-schema\">\n\t\t\t{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/kedar.nitty-witty.com\\\/blog\\\/relay-log-read-failure-2-many-dots-can-break-your-replication-only-once#article\",\"name\":\"Relay log read failure | 2 many dots can break your replication only once | Change Is Inevitable\",\"headline\":\"Relay log read failure | 2 many dots can break your replication only once\",\"author\":{\"@id\":\"https:\\\/\\\/kedar.nitty-witty.com\\\/blog\\\/author\\\/admin#author\"},\"publisher\":{\"@id\":\"https:\\\/\\\/kedar.nitty-witty.com\\\/blog\\\/#person\"},\"image\":{\"@type\":\"ImageObject\",\"@id\":\"https:\\\/\\\/kedar.nitty-witty.com\\\/blog\\\/relay-log-read-failure-2-many-dots-can-break-your-replication-only-once#articleImage\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/be1f7021485c325d92cc4c5d961accb9c1af72b1b11281a790f7f4f066ef10d3?s=96&d=mm&r=g\",\"width\":96,\"height\":96,\"caption\":\"Kedar\"},\"datePublished\":\"2021-08-19T13:12:49+00:00\",\"dateModified\":\"2023-05-18T14:36:30+00:00\",\"inLanguage\":\"en-US\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/kedar.nitty-witty.com\\\/blog\\\/relay-log-read-failure-2-many-dots-can-break-your-replication-only-once#webpage\"},\"isPartOf\":{\"@id\":\"https:\\\/\\\/kedar.nitty-witty.com\\\/blog\\\/relay-log-read-failure-2-many-dots-can-break-your-replication-only-once#webpage\"},\"articleSection\":\"MySQL, MySQL-Articles, binary log, GTID Replication, MySQL, mysql bug, Relay log read failure, relay-log, replication\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/kedar.nitty-witty.com\\\/blog\\\/relay-log-read-failure-2-many-dots-can-break-your-replication-only-once#breadcrumblist\",\"itemListElement\":[{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/kedar.nitty-witty.com\\\/blog#listItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/kedar.nitty-witty.com\\\/blog\",\"nextItem\":{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/kedar.nitty-witty.com\\\/blog\\\/category\\\/mysql#listItem\",\"name\":\"MySQL\"}},{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/kedar.nitty-witty.com\\\/blog\\\/category\\\/mysql#listItem\",\"position\":2,\"name\":\"MySQL\",\"item\":\"https:\\\/\\\/kedar.nitty-witty.com\\\/blog\\\/category\\\/mysql\",\"nextItem\":{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/kedar.nitty-witty.com\\\/blog\\\/category\\\/mysql\\\/mysql-articles#listItem\",\"name\":\"MySQL-Articles\"},\"previousItem\":{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/kedar.nitty-witty.com\\\/blog#listItem\",\"name\":\"Home\"}},{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/kedar.nitty-witty.com\\\/blog\\\/category\\\/mysql\\\/mysql-articles#listItem\",\"position\":3,\"name\":\"MySQL-Articles\",\"item\":\"https:\\\/\\\/kedar.nitty-witty.com\\\/blog\\\/category\\\/mysql\\\/mysql-articles\",\"nextItem\":{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/kedar.nitty-witty.com\\\/blog\\\/relay-log-read-failure-2-many-dots-can-break-your-replication-only-once#listItem\",\"name\":\"Relay log read failure | 2 many dots can break your replication only once\"},\"previousItem\":{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/kedar.nitty-witty.com\\\/blog\\\/category\\\/mysql#listItem\",\"name\":\"MySQL\"}},{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/kedar.nitty-witty.com\\\/blog\\\/relay-log-read-failure-2-many-dots-can-break-your-replication-only-once#listItem\",\"position\":4,\"name\":\"Relay log read failure | 2 many dots can break your replication only once\",\"previousItem\":{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/kedar.nitty-witty.com\\\/blog\\\/category\\\/mysql\\\/mysql-articles#listItem\",\"name\":\"MySQL-Articles\"}}]},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/kedar.nitty-witty.com\\\/blog\\\/#person\",\"name\":\"Kedar\",\"image\":{\"@type\":\"ImageObject\",\"@id\":\"https:\\\/\\\/kedar.nitty-witty.com\\\/blog\\\/relay-log-read-failure-2-many-dots-can-break-your-replication-only-once#personImage\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/be1f7021485c325d92cc4c5d961accb9c1af72b1b11281a790f7f4f066ef10d3?s=96&d=mm&r=g\",\"width\":96,\"height\":96,\"caption\":\"Kedar\"}},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/kedar.nitty-witty.com\\\/blog\\\/author\\\/admin#author\",\"url\":\"https:\\\/\\\/kedar.nitty-witty.com\\\/blog\\\/author\\\/admin\",\"name\":\"Kedar\",\"image\":{\"@type\":\"ImageObject\",\"@id\":\"https:\\\/\\\/kedar.nitty-witty.com\\\/blog\\\/relay-log-read-failure-2-many-dots-can-break-your-replication-only-once#authorImage\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/be1f7021485c325d92cc4c5d961accb9c1af72b1b11281a790f7f4f066ef10d3?s=96&d=mm&r=g\",\"width\":96,\"height\":96,\"caption\":\"Kedar\"}},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/kedar.nitty-witty.com\\\/blog\\\/relay-log-read-failure-2-many-dots-can-break-your-replication-only-once#webpage\",\"url\":\"https:\\\/\\\/kedar.nitty-witty.com\\\/blog\\\/relay-log-read-failure-2-many-dots-can-break-your-replication-only-once\",\"name\":\"Relay log read failure | 2 many dots can break your replication only once | Change Is Inevitable\",\"description\":\"Two or more dots in your relay log or binary log names can break replication; but worry not, it will only do it once. If you request to start again, it will work. That's it, that's the blog. Should you choose to spend some more time, go ahead. Last_SQL_Error: Relay log read failure: Could not Having two or more dots in your relay-log or log-bin configuration will break the replication once. This is the blog to anticipate on this bug I posted.\",\"inLanguage\":\"en-US\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/kedar.nitty-witty.com\\\/blog\\\/#website\"},\"breadcrumb\":{\"@id\":\"https:\\\/\\\/kedar.nitty-witty.com\\\/blog\\\/relay-log-read-failure-2-many-dots-can-break-your-replication-only-once#breadcrumblist\"},\"author\":{\"@id\":\"https:\\\/\\\/kedar.nitty-witty.com\\\/blog\\\/author\\\/admin#author\"},\"creator\":{\"@id\":\"https:\\\/\\\/kedar.nitty-witty.com\\\/blog\\\/author\\\/admin#author\"},\"datePublished\":\"2021-08-19T13:12:49+00:00\",\"dateModified\":\"2023-05-18T14:36:30+00:00\"},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/kedar.nitty-witty.com\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/kedar.nitty-witty.com\\\/blog\\\/\",\"name\":\"..::CHANGE is INEVITABLE::..\",\"description\":\"Kedar Vaijanapurkar's Blog for MySQL, technology and various subjects\",\"inLanguage\":\"en-US\",\"publisher\":{\"@id\":\"https:\\\/\\\/kedar.nitty-witty.com\\\/blog\\\/#person\"}}]}\n\t\t<\/script>\n\t\t<!-- All in One SEO -->\n\n","aioseo_head_json":{"title":"Relay log read failure | 2 many dots can break your replication only once | Change Is Inevitable","description":"Two or more dots in your relay log or binary log names can break replication; but worry not, it will only do it once. If you request to start again, it will work. That's it, that's the blog. Should you choose to spend some more time, go ahead. Last_SQL_Error: Relay log read failure: Could not Having two or more dots in your relay-log or log-bin configuration will break the replication once. This is the blog to anticipate on this bug I posted.","canonical_url":"https:\/\/kedar.nitty-witty.com\/blog\/relay-log-read-failure-2-many-dots-can-break-your-replication-only-once","robots":"max-image-preview:large","keywords":"binary log,gtid replication,mysql,mysql bug,relay log read failure,relay-log,replication","webmasterTools":{"google-site-verification":"_Bu1h5r0PxIC0D2jBVdmYN45RTeG9ogcX85XLkbG1qA","msvalidate.01":"116B62074CBCA1BA99B8CCE09CCF2FB8","miscellaneous":""},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/kedar.nitty-witty.com\/blog\/relay-log-read-failure-2-many-dots-can-break-your-replication-only-once#article","name":"Relay log read failure | 2 many dots can break your replication only once | Change Is Inevitable","headline":"Relay log read failure | 2 many dots can break your replication only once","author":{"@id":"https:\/\/kedar.nitty-witty.com\/blog\/author\/admin#author"},"publisher":{"@id":"https:\/\/kedar.nitty-witty.com\/blog\/#person"},"image":{"@type":"ImageObject","@id":"https:\/\/kedar.nitty-witty.com\/blog\/relay-log-read-failure-2-many-dots-can-break-your-replication-only-once#articleImage","url":"https:\/\/secure.gravatar.com\/avatar\/be1f7021485c325d92cc4c5d961accb9c1af72b1b11281a790f7f4f066ef10d3?s=96&d=mm&r=g","width":96,"height":96,"caption":"Kedar"},"datePublished":"2021-08-19T13:12:49+00:00","dateModified":"2023-05-18T14:36:30+00:00","inLanguage":"en-US","mainEntityOfPage":{"@id":"https:\/\/kedar.nitty-witty.com\/blog\/relay-log-read-failure-2-many-dots-can-break-your-replication-only-once#webpage"},"isPartOf":{"@id":"https:\/\/kedar.nitty-witty.com\/blog\/relay-log-read-failure-2-many-dots-can-break-your-replication-only-once#webpage"},"articleSection":"MySQL, MySQL-Articles, binary log, GTID Replication, MySQL, mysql bug, Relay log read failure, relay-log, replication"},{"@type":"BreadcrumbList","@id":"https:\/\/kedar.nitty-witty.com\/blog\/relay-log-read-failure-2-many-dots-can-break-your-replication-only-once#breadcrumblist","itemListElement":[{"@type":"ListItem","@id":"https:\/\/kedar.nitty-witty.com\/blog#listItem","position":1,"name":"Home","item":"https:\/\/kedar.nitty-witty.com\/blog","nextItem":{"@type":"ListItem","@id":"https:\/\/kedar.nitty-witty.com\/blog\/category\/mysql#listItem","name":"MySQL"}},{"@type":"ListItem","@id":"https:\/\/kedar.nitty-witty.com\/blog\/category\/mysql#listItem","position":2,"name":"MySQL","item":"https:\/\/kedar.nitty-witty.com\/blog\/category\/mysql","nextItem":{"@type":"ListItem","@id":"https:\/\/kedar.nitty-witty.com\/blog\/category\/mysql\/mysql-articles#listItem","name":"MySQL-Articles"},"previousItem":{"@type":"ListItem","@id":"https:\/\/kedar.nitty-witty.com\/blog#listItem","name":"Home"}},{"@type":"ListItem","@id":"https:\/\/kedar.nitty-witty.com\/blog\/category\/mysql\/mysql-articles#listItem","position":3,"name":"MySQL-Articles","item":"https:\/\/kedar.nitty-witty.com\/blog\/category\/mysql\/mysql-articles","nextItem":{"@type":"ListItem","@id":"https:\/\/kedar.nitty-witty.com\/blog\/relay-log-read-failure-2-many-dots-can-break-your-replication-only-once#listItem","name":"Relay log read failure | 2 many dots can break your replication only once"},"previousItem":{"@type":"ListItem","@id":"https:\/\/kedar.nitty-witty.com\/blog\/category\/mysql#listItem","name":"MySQL"}},{"@type":"ListItem","@id":"https:\/\/kedar.nitty-witty.com\/blog\/relay-log-read-failure-2-many-dots-can-break-your-replication-only-once#listItem","position":4,"name":"Relay log read failure | 2 many dots can break your replication only once","previousItem":{"@type":"ListItem","@id":"https:\/\/kedar.nitty-witty.com\/blog\/category\/mysql\/mysql-articles#listItem","name":"MySQL-Articles"}}]},{"@type":"Person","@id":"https:\/\/kedar.nitty-witty.com\/blog\/#person","name":"Kedar","image":{"@type":"ImageObject","@id":"https:\/\/kedar.nitty-witty.com\/blog\/relay-log-read-failure-2-many-dots-can-break-your-replication-only-once#personImage","url":"https:\/\/secure.gravatar.com\/avatar\/be1f7021485c325d92cc4c5d961accb9c1af72b1b11281a790f7f4f066ef10d3?s=96&d=mm&r=g","width":96,"height":96,"caption":"Kedar"}},{"@type":"Person","@id":"https:\/\/kedar.nitty-witty.com\/blog\/author\/admin#author","url":"https:\/\/kedar.nitty-witty.com\/blog\/author\/admin","name":"Kedar","image":{"@type":"ImageObject","@id":"https:\/\/kedar.nitty-witty.com\/blog\/relay-log-read-failure-2-many-dots-can-break-your-replication-only-once#authorImage","url":"https:\/\/secure.gravatar.com\/avatar\/be1f7021485c325d92cc4c5d961accb9c1af72b1b11281a790f7f4f066ef10d3?s=96&d=mm&r=g","width":96,"height":96,"caption":"Kedar"}},{"@type":"WebPage","@id":"https:\/\/kedar.nitty-witty.com\/blog\/relay-log-read-failure-2-many-dots-can-break-your-replication-only-once#webpage","url":"https:\/\/kedar.nitty-witty.com\/blog\/relay-log-read-failure-2-many-dots-can-break-your-replication-only-once","name":"Relay log read failure | 2 many dots can break your replication only once | Change Is Inevitable","description":"Two or more dots in your relay log or binary log names can break replication; but worry not, it will only do it once. If you request to start again, it will work. That's it, that's the blog. Should you choose to spend some more time, go ahead. Last_SQL_Error: Relay log read failure: Could not Having two or more dots in your relay-log or log-bin configuration will break the replication once. This is the blog to anticipate on this bug I posted.","inLanguage":"en-US","isPartOf":{"@id":"https:\/\/kedar.nitty-witty.com\/blog\/#website"},"breadcrumb":{"@id":"https:\/\/kedar.nitty-witty.com\/blog\/relay-log-read-failure-2-many-dots-can-break-your-replication-only-once#breadcrumblist"},"author":{"@id":"https:\/\/kedar.nitty-witty.com\/blog\/author\/admin#author"},"creator":{"@id":"https:\/\/kedar.nitty-witty.com\/blog\/author\/admin#author"},"datePublished":"2021-08-19T13:12:49+00:00","dateModified":"2023-05-18T14:36:30+00:00"},{"@type":"WebSite","@id":"https:\/\/kedar.nitty-witty.com\/blog\/#website","url":"https:\/\/kedar.nitty-witty.com\/blog\/","name":"..::CHANGE is INEVITABLE::..","description":"Kedar Vaijanapurkar's Blog for MySQL, technology and various subjects","inLanguage":"en-US","publisher":{"@id":"https:\/\/kedar.nitty-witty.com\/blog\/#person"}}]},"og:locale":"en_US","og:site_name":"Change Is Inevitable | Kedar Vaijanapurkar's Blog for MySQL, technology and various subjects","og:type":"article","og:title":"Relay log read failure | 2 many dots can break your replication only once | Change Is Inevitable","og:description":"Two or more dots in your relay log or binary log names can break replication; but worry not, it will only do it once. If you request to start again, it will work. That's it, that's the blog. Should you choose to spend some more time, go ahead. Last_SQL_Error: Relay log read failure: Could not Having two or more dots in your relay-log or log-bin configuration will break the replication once. This is the blog to anticipate on this bug I posted.","og:url":"https:\/\/kedar.nitty-witty.com\/blog\/relay-log-read-failure-2-many-dots-can-break-your-replication-only-once","article:published_time":"2021-08-19T13:12:49+00:00","article:modified_time":"2023-05-18T14:36:30+00:00","twitter:card":"summary","twitter:title":"Relay log read failure | 2 many dots can break your replication only once | Change Is Inevitable","twitter:description":"Two or more dots in your relay log or binary log names can break replication; but worry not, it will only do it once. If you request to start again, it will work. That's it, that's the blog. Should you choose to spend some more time, go ahead. Last_SQL_Error: Relay log read failure: Could not Having two or more dots in your relay-log or log-bin configuration will break the replication once. This is the blog to anticipate on this bug I posted."},"aioseo_meta_data":{"post_id":"2557","title":null,"description":"#post_excerpt Having two or more dots in your relay-log or log-bin configuration will break the replication once. This is the blog to anticipate on this bug I posted.","keywords":[],"keyphrases":{"focus":[],"additional":[]},"primary_term":null,"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":"","og_custom_url":null,"og_article_section":null,"og_article_tags":[],"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":{"id":"aioseo-article-6385d28a3bf92","slug":"article","graphName":"Article","label":"Article","properties":{"type":"BlogPosting","name":"#post_title","headline":"#post_title","description":"#post_excerpt","image":"","keywords":"","author":{"name":"#author_name","url":"#author_url"},"dates":{"include":true,"datePublished":"","dateModified":""}}},"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"","isEnabled":true},"graphs":[]},"schema_type":"default","schema_type_options":"{\"article\":{\"articleType\":\"BlogPosting\"},\"course\":{\"name\":\"\",\"description\":\"\",\"provider\":\"\"},\"faq\":{\"pages\":[]},\"product\":{\"reviews\":[]},\"recipe\":{\"ingredients\":[],\"instructions\":[],\"keywords\":[]},\"software\":{\"reviews\":[],\"operatingSystems\":[]},\"webPage\":{\"webPageType\":\"WebPage\"}}","pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":"-1","robots_max_videopreview":"-1","robots_max_imagepreview":"large","priority":null,"frequency":"default","location":null,"local_seo":{"businessInfo":{"name":"","urls":{"website":"","aboutPage":"","contactPage":""},"address":{"line1":"","line2":"","zip":"","city":"","state":"","country":""},"contact":{"email":"","phone":"","fax":""},"ids":{"vatID":"","taxID":"","chamberID":""},"payment":{"priceIndication":"","currenciesAccepted":"","methodsAccepted":""},"areaServed":""},"openingHours":{"show":false,"closedLabel":"","open24h":false,"open24hLabel":"","open247":false,"use24hFormat":false,"twoSets":false,"timezone":"","hours":[]}},"breadcrumb_settings":null,"limit_modified_date":false,"ai":null,"created":"2021-08-19 12:24:02","updated":"2025-08-16 19:18:27","seo_analyzer_scan_date":null},"aioseo_breadcrumb":"<div class=\"aioseo-breadcrumbs\"><span class=\"aioseo-breadcrumb\">\n\t\t\t<a href=\"https:\/\/kedar.nitty-witty.com\/blog\" title=\"Home\">Home<\/a>\n\t\t<\/span><span class=\"aioseo-breadcrumb-separator\">\u00bb<\/span><span class=\"aioseo-breadcrumb\">\n\t\t\t<a href=\"https:\/\/kedar.nitty-witty.com\/blog\/category\/mysql\" title=\"MySQL\">MySQL<\/a>\n\t\t<\/span><span class=\"aioseo-breadcrumb-separator\">\u00bb<\/span><span class=\"aioseo-breadcrumb\">\n\t\t\t<a href=\"https:\/\/kedar.nitty-witty.com\/blog\/category\/mysql\/mysql-articles\" title=\"MySQL-Articles\">MySQL-Articles<\/a>\n\t\t<\/span><span class=\"aioseo-breadcrumb-separator\">\u00bb<\/span><span class=\"aioseo-breadcrumb\">\n\t\t\tRelay log read failure | 2 many dots can break your replication only once\n\t\t<\/span><\/div>","aioseo_breadcrumb_json":[{"label":"Home","link":"https:\/\/kedar.nitty-witty.com\/blog"},{"label":"MySQL","link":"https:\/\/kedar.nitty-witty.com\/blog\/category\/mysql"},{"label":"MySQL-Articles","link":"https:\/\/kedar.nitty-witty.com\/blog\/category\/mysql\/mysql-articles"},{"label":"Relay log read failure | 2 many dots can break your replication only once","link":"https:\/\/kedar.nitty-witty.com\/blog\/relay-log-read-failure-2-many-dots-can-break-your-replication-only-once"}],"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/kedar.nitty-witty.com\/blog\/wp-json\/wp\/v2\/posts\/2557","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/kedar.nitty-witty.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/kedar.nitty-witty.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/kedar.nitty-witty.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/kedar.nitty-witty.com\/blog\/wp-json\/wp\/v2\/comments?post=2557"}],"version-history":[{"count":7,"href":"https:\/\/kedar.nitty-witty.com\/blog\/wp-json\/wp\/v2\/posts\/2557\/revisions"}],"predecessor-version":[{"id":2903,"href":"https:\/\/kedar.nitty-witty.com\/blog\/wp-json\/wp\/v2\/posts\/2557\/revisions\/2903"}],"wp:attachment":[{"href":"https:\/\/kedar.nitty-witty.com\/blog\/wp-json\/wp\/v2\/media?parent=2557"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/kedar.nitty-witty.com\/blog\/wp-json\/wp\/v2\/categories?post=2557"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/kedar.nitty-witty.com\/blog\/wp-json\/wp\/v2\/tags?post=2557"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}