| 2015-04-14 09:36:56 |
Miguel Angel Nieto |
bug |
|
|
added bug |
| 2015-04-14 09:37:28 |
Miguel Angel Nieto |
description |
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 :) |
We have a master with multiple slaves. While the checksum process is ongoing if we stop a slave server the checksum process is also 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 :) |
|
| 2015-04-14 09:37:44 |
Miguel Angel Nieto |
description |
We have a master with multiple slaves. While the checksum process is ongoing if we stop a slave server the checksum process is also 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 :) |
We have a master with multiple slaves. While the checksum process is ongoing if we stop a slave server the checksum process is also 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 :) |
|
| 2015-04-14 09:40:09 |
Miguel Angel Nieto |
description |
We have a master with multiple slaves. While the checksum process is ongoing if we stop a slave server the checksum process is also 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 :) |
We have a master with multiple slaves. While the checksum process is ongoing if we stop a slave server the checksum process is also 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 if 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 :) |
|
| 2015-04-14 10:40:00 |
Brian Bird |
bug |
|
|
added subscriber Brian Bird |
| 2015-04-27 19:39:53 |
Frank Cizmich |
tags |
i52954 |
i52954 pt-table-checksum |
|
| 2015-04-28 06:53:31 |
Nilnandan Joshi |
percona-toolkit: status |
New |
Confirmed |
|
| 2015-04-28 06:53:35 |
Nilnandan Joshi |
bug |
|
|
added subscriber Nilnandan Joshi |
| 2015-09-02 17:24:12 |
Frank Cizmich |
marked as duplicate |
|
1042727 |
|
