Failed to read packet: Got error reading packet from server: The slave is connecting using CHANGE MASTER TO MASTER_AUTO_POSITION about mysql-ripple HOT 11 OPEN

I was able to reproduce this. It looks like we have assumed that MySQL will treat empty gtid_executed as "start replicating from the first binlog file you have", but MySQL doesn't do that. I'll look if it's possible to fix this, but for now please take some value of gtid_executed from the master (either just as the current value of the variable or the GTID list from the first binlog file) and pass it to -ripple_requested_start_gtid_position flag. Then Ripple will be able to successfully start replicating from that position onward.

from mysql-ripple.

I have a master SQL instance in google cloud, while I try to set up a bin log server using MySQL-ripple I'm facing the issue, also I need to set up a slave from bin log server is this possible?

from mysql-ripple.

You definitely can set up slave from Ripple. Just execute CHANGE MASTER TO on the replica and use Ripple's IP and port as MASTER_HOST and MASTER_PORT in the statement, also use MASTER_AUTO_POSITION = 1. With that the replica should be able to successfully start replicating from Ripple.

Regarding the issue that Ripple has trying to replicate from the master: it's not clear for me why this could happen. Can you post excerpt from the master's error log? I think it should have more info on what's happening.

from mysql-ripple.

but im facing the above issue while running the following command in MySQL-ripple folder /Bazel-bin/rippled -ripple_datadir=./data -ripple_master_address... also I'm using the master instance in google cloud

from mysql-ripple.

Right. And the problem is that for some reason the master thinks that Ripple asks to start replicating with a certain GTID that is not in the master's binlogs. I think mysql.err log on the master will have more details about what it doesn't like. Can you post those logs here? Here's documentation on how to find and export the logs: https://cloud.google.com/sql/docs/mysql/instance-info#mysqllogs.

from mysql-ripple.

Sure, I will post the logs here.

from mysql-ripple.

{
insertId: "s=35b0979499e449f597024875fb0def4a;i=2651a2;b=3df4b4a8e7c441b7af3023f4be28012c;m=23e2252d274;t=59488d134f425;x=2e839cd52ec7c6ad-0@a1"
logName: "projects/project-178317/logs/cloudsql.googleapis.com%2Fmysql.err"
receiveTimestamp: "2019-10-10T06:50:31.380054318Z"
resource: {…}
severity: "ERROR"
textPayload: "2019-10-10T06:50:29.924655Z 1105466 [Note] my server_id: 604687941, my uuid: b5105251-e63e-11e8-9d29-42010a800494 slave with server_id: 112211 uuid: connects with GTID_executed: "
timestamp: "2019-10-10T06:50:29.924901Z"
}

from mysql-ripple.

The log looks like this
2019-10-10T06:52:28.167847Z 1105623 [Note] my server_id: 604687941, my uuid: b5105251-e63e-11e8-9d29-42010a800494 slave with server_id: 112211 uuid: connects with GTID_executed:

from mysql-ripple.

Is that the only log message related to Ripple's attempt to connect? It doesn't bring any clarity unfortunately. :(
I guess I'll try to reproduce this myself to understand what's happening...

from mysql-ripple.

Yes, the below log is frequently producing.
2019-10-10T06:52:28.167847Z 1105623 [Note] my server_id: 604687941, my uuid: b5105251-e63e-11e8-9d29-42010a800494 slave with server_id: 112211 uuid: connects with GTID_executed:

from mysql-ripple.

I will try it

from mysql-ripple.