Update warning about using this tool in its docs.

This commit is contained in:
Daniel Nichter
2012-12-11 17:27:57 -07:00
parent 6c6ae95ea3
commit 371f4a9e15

View File

@@ -4943,7 +4943,7 @@ pt-slave-restart - Watch and restart MySQL replication after errors.
=head1 SYNOPSIS =head1 SYNOPSIS
Usage: pt-slave-restart [OPTION...] [DSN] Usage: pt-slave-restart [OPTIONS] [DSN]
pt-slave-restart watches one or more MySQL replication slaves for pt-slave-restart watches one or more MySQL replication slaves for
errors, and tries to restart replication if it stops. errors, and tries to restart replication if it stops.
@@ -4960,9 +4960,6 @@ it is having problems with replication. Don't be too hasty to use it unless you
need to. If you use this tool carelessly, you might miss the chance to really need to. If you use this tool carelessly, you might miss the chance to really
solve the slave server's problems. solve the slave server's problems.
At the time of this release there is a bug that causes an invalid
C<CHANGE MASTER TO> statement to be executed.
The authoritative source for updated information is always the online issue The authoritative source for updated information is always the online issue
tracking system. Issues that affect this tool will be marked as such. You can tracking system. Issues that affect this tool will be marked as such. You can
see a list of such issues at the following URL: see a list of such issues at the following URL:
@@ -4977,12 +4974,9 @@ statements that cause errors. It polls slaves intelligently with an
exponentially varying sleep time. You can specify errors to skip and run the exponentially varying sleep time. You can specify errors to skip and run the
slaves until a certain binlog position. slaves until a certain binlog position.
Note: it has come to my attention that Yahoo! had or has an internal tool Although this tool can help a slave advance past errors, you should not
called fix_repl, described to me by a past Yahoo! employee and mentioned in rely on it to "fix" replication. If slave errors occur frequently or
the first edition of High Performance MySQL. Apparently this tool does the unexpectedly, you should identify and fix the root cause.
same thing. Make no mistake, though: this is not a way to "fix replication."
In fact I would not even encourage its use on a regular basis; I use it only
when I have an error I know I just need to skip past.
=head1 OUTPUT =head1 OUTPUT