All work
- LP #1048198: pt-slave-restart shouldn't exit on unknown error textPT-1021
- LP #1046966: pt-stalk fails when there is too many connectionPT-1020
- LP #1046483: pt-archiver doesn't reconnect and retry its SELECT queriesPT-1019
- LP #1042727: pt-table-checksum doesn't reconnect the slave $dbhPT-329Resolved issue: PT-329
- LP #941469: pt-kill doesn't reconnect if its connection is lostPT-299Resolved issue: PT-299
5 of 5
LP #1048198: pt-slave-restart shouldn't exit on unknown error text
General
Escalation
General
Escalation
Description
Environment
None
Details
Details
Assignee
Unassigned
UnassignedReporter
lpjirasync
lpjirasync(Deactivated)Priority
Created January 24, 2018 at 6:55 PM
Updated December 21, 2019 at 2:32 PM
Activity
Show:
**Reported in Launchpad by Baron Schwartz last update 01-10-2012 19:30:59
pt-slave-restart is designed to quit if --error-text is given but the error message doesn't match that. I run it as a daemon for several known types of errors (deadlocks, lock wait timeouts) and occasionally I get some other problem. I don't want it to quit and have to be restarted. It should just not do anything if it doesn't know what to do. Otherwise when an occasional problem happens, and I correct it manually, now I have to go restart the daemon manually instead of it picking up from there and fixing deadlock/timeout problems.