Layer7 API Management

  • 1.  CA API Gateway replication failure on Secondary node

    Posted Dec 04, 2017 10:58 AM

    The replication status on the secondary node is showing "Slave_IO_Running: No",

    Should I clone the primary node database and rebuild the secondary node once again? Please advise.

     

    [root@********* ~]# mysql -e "show slave status\G;"
    *************************** 1. row ***************************
    Slave_IO_State:
    Master_Host: *********
    Master_User: repluser
    Master_Port: 3307
    Connect_Retry: 100
    Master_Log_File: ssgbin-log.000054
    Read_Master_Log_Pos: 203505493
    Relay_Log_File: ssgrelay-bin.000157
    Relay_Log_Pos: 4
    Relay_Master_Log_File: ssgbin-log.000054
    Slave_IO_Running: No
    Slave_SQL_Running: Yes
    Replicate_Do_DB:
    Replicate_Ignore_DB:
    Replicate_Do_Table:
    Replicate_Ignore_Table:
    Replicate_Wild_Do_Table:
    Replicate_Wild_Ignore_Table:
    Last_Errno: 0
    Last_Error:
    Skip_Counter: 0
    Exec_Master_Log_Pos: 203505493
    Relay_Log_Space: 107
    Until_Condition: None
    Until_Log_File:
    Until_Log_Pos: 0
    Master_SSL_Allowed: No
    Master_SSL_CA_File:
    Master_SSL_CA_Path:
    Master_SSL_Cert:
    Master_SSL_Cipher:
    Master_SSL_Key:
    Seconds_Behind_Master: NULL
    Master_SSL_Verify_Server_Cert: No
    Last_IO_Errno: 1236
    Last_IO_Error: Got fatal error 1236 from master when reading data from binary log: 'Client requested master to start replication from impossible position; the first event 'ssgbin-log.000054' at 203505493, the last event read from '/var/lib/mysql/ssgbin-log.000054' at 4, the last byte read from '/var/lib/mysql/ssgbin-log.000054' at 4.'
    Last_SQL_Errno: 0
    Last_SQL_Error:
    Replicate_Ignore_Server_Ids:
    Master_Server_Id: 1

     

    Thanks,

    Jo



  • 2.  Re: CA API Gateway replication failure on Secondary node
    Best Answer

    Posted Dec 04, 2017 03:15 PM

    Hi,

    You can try to reinitialize the replication and check the status again, this should resolve your issue.

    Reinitialize replication in a multi-node cluster 

    Hope this helps

    Thanks

    Abs



  • 3.  Re: CA API Gateway replication failure on Secondary node

    Posted Dec 05, 2017 11:58 AM

    Hi Abs,

     

    The issue is reported only on secondary node, should I also reset master and execute create_slave script on the primary node?

     

    Thanks,

    Jo



  • 4.  Re: CA API Gateway replication failure on Secondary node

    Posted Dec 05, 2017 12:13 PM

    Yes, Please go through the all the steps on the document and run all steps on both primary and secondary as stated to confirm it reinitialize the replication and working correctly



  • 5.  Re: CA API Gateway replication failure on Secondary node

    Posted Dec 05, 2017 12:15 PM

    thank you abs



  • 6.  Re: CA API Gateway replication failure on Secondary node

    Posted Dec 05, 2017 12:23 PM

    No Problem, Please mark this as answered if you are satisfied with the information provided.

    Thanks

    Abs



  • 7.  Re: CA API Gateway replication failure on Secondary node

    Posted May 09, 2018 02:39 PM

    We have the same problem right now:

    Last_IO_Errno: 1236
    Last_IO_Error: Got fatal error 1236 from master when reading data from binary log: 'Client requested master to start replication from position > file size'



  • 8.  Re: CA API Gateway replication failure on Secondary node

    Broadcom Employee
    Posted May 09, 2018 06:55 PM

    seems the bin log file corrupted, you may need to re-init replication again, before that please double check the disk space.