Comments on: Live MySQL Slave Rebuild with Percona Toolkit https://www.percona.com/blog/live-mysql-slave-rebuild-with-percona-toolkit/ Tue, 06 Aug 2019 20:02:17 +0000 hourly 1 https://wordpress.org/?v=6.5.2 By: Neo Anderson https://www.percona.com/blog/live-mysql-slave-rebuild-with-percona-toolkit/#comment-10970466 Thu, 14 Mar 2019 12:03:36 +0000 https://www.percona.com/blog/?p=55560#comment-10970466 In place of pt-slave-restart you can also use inbuilt MySQL parameter slave_exec_mode=IDEMPOTENT

This will keep the replication running even in case of errors, these errors, like you described, can be fixed using pt-table-checksum and pt-table-sync.

]]>
By: spine care centre https://www.percona.com/blog/live-mysql-slave-rebuild-with-percona-toolkit/#comment-10970464 Thu, 14 Mar 2019 04:05:43 +0000 https://www.percona.com/blog/?p=55560#comment-10970464 Perfect tool kit

]]>
By: Ralf Buescher https://www.percona.com/blog/live-mysql-slave-rebuild-with-percona-toolkit/#comment-10970461 Wed, 13 Mar 2019 12:30:21 +0000 https://www.percona.com/blog/?p=55560#comment-10970461 It might be an idea to have apps use dedicated credentials and priviledges. This way an account can read but not write – it might help to make a developer to revonsider his options, when hit with a a „No Insert/ Update/ Create/ Drop/ Alter Permission Granted“ error. Errors are not in any case a human error, but rather the result of a lack of information.

]]>