We have a master with multiple slaves. While the checksum process is ongoing if we stop a slave server the process is stopped:
ExitStatus:111 04-14T03:00:02 DBI connect(';host=x.x.x.x.x;mysql_read_default_group=client','xxxxx',...) failed: Can't connect to MySQL server on 'x.x.x.x' (111) at /usr/local/bin/pt-table-checksum line 1586
If the tool is disconnected from a slave, it should just wait there until it reconnects again, with a good timeout like 1 hour. That timeout could be configured with a new variable. The tool should only wait with the error is "Can't connect to MySQL server" but not when the error is related with user privileges (those are not going to be fixed automatically).
We have a master with multiple slaves. While the checksum process is ongoing if we stop a slave server the process is stopped:
ExitStatus:111 04-14T03:00:02 DBI connect( ';host= x.x.x.x. x;mysql_ read_default_ group=client' ,'xxxxx' ,...) failed: Can't connect to MySQL server on 'x.x.x.x' (111) at /usr/local/ bin/pt- table-checksum line 1586
If the tool is disconnected from a slave, it should just wait there until it reconnects again, with a good timeout like 1 hour. That timeout could be configured with a new variable. The tool should only wait with the error is "Can't connect to MySQL server" but not when the error is related with user privileges (those are not going to be fixed automatically).
Comments are welcome :)