From aab0b0cd22e6abb259df279c6920ddc0a897a329 Mon Sep 17 00:00:00 2001 From: Sveta Smirnova Date: Sun, 6 Oct 2024 22:55:48 +0300 Subject: [PATCH] PT-2340 - Support MySQL 8.4 - Fixed typos --- bin/pt-config-diff | 2 +- bin/pt-heartbeat | 4 ++-- bin/pt-replica-restart | 2 +- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/bin/pt-config-diff b/bin/pt-config-diff index 434d5025..927a3191 100755 --- a/bin/pt-config-diff +++ b/bin/pt-config-diff @@ -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 diff --git a/bin/pt-heartbeat b/bin/pt-heartbeat index c20273ca..d8b931f3 100755 --- a/bin/pt-heartbeat +++ b/bin/pt-heartbeat @@ -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 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. diff --git a/bin/pt-replica-restart b/bin/pt-replica-restart index 0dfdb45c..6a836602 100755 --- a/bin/pt-replica-restart +++ b/bin/pt-replica-restart @@ -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.