percona/percona-toolkit
1
0
Fork 0
mirror of https://github.com/percona/percona-toolkit.git synced 2025-09-16 16:23:30 +00:00
Code Issues Packages Projects Releases Wiki Activity

PT-2340 - Support MySQL 8.4

Browse Source 
- Fixed typos
This commit is contained in:
Sveta Smirnova
2024-10-06 22:55:48 +03:00
parent ec677f4979
commit aab0b0cd22
3 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
bin/pt-config-diff
View File

@@ -5692,7 +5692,7 @@ There is no output when there are no differences. When there are differences,
pt-config-diff prints a report to STDOUT that looks similar to the following:
2 config differences
Variable my.soource.cnf my.replica.cnf
Variable my.source.cnf my.replica.cnf
========================= =============== ===============
datadir /tmp/12345/data /tmp/12346/data
port 12345 12346

4
bin/pt-heartbeat
View File

@@ -6978,7 +6978,7 @@ pt-heartbeat measures replication lag on a MySQL or PostgreSQL server. You can
use it to update a replication source or monitor a replica. If possible, MySQL
connection options are read from your .my.cnf file.
Start daemonized process to update test.heartbeat table on replicaiton source:
Start daemonized process to update test.heartbeat table on replication source:
pt-heartbeat -D test --update -h source-server --daemonize
@@ -7018,7 +7018,7 @@ avoids reliance on the replication mechanism itself, which is unreliable. (For
example, C<SHOW REPLICA STATUS> on MySQL).
The first part is an L<"--update"> instance of pt-heartbeat that connects to
a replicaiton source and updates a timestamp ("heartbeat record") every
a replication source and updates a timestamp ("heartbeat record") every
L<"--interval"> seconds. Since the heartbeat table may contain records from
multiple replication sources (see L<"MULTI-REPLICA HIERARCHY">), the server's ID
(@@server_id) is used to identify records.

2
bin/pt-replica-restart
View File

@@ -6131,7 +6131,7 @@ Possible methods are:
hosts SHOW REPLICAS (SHOW SLAVE HOSTS before MySQL 8.1)
none Do not find replicas
The processlist method is preferred because SHOW REPLCIAS is not reliable.
The processlist method is preferred because SHOW REPLICAS is not reliable.
However, the hosts method is required if the server uses a non-standard
port (not 3306). Usually pt-replica-restart does the right thing and finds
the replicas, but you may give a preferred method and it will be used first.