pt-agent requires restart after changing MySQL options
Bug #1248363 reported by
Daniel Nichter
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Percona Toolkit moved to https://jira.percona.com/projects/PT |
Fix Released
|
High
|
Daniel Nichter | ||
Bug Description
Chaning an agent's config, specifically the MySLQL options like --socket, should be applied automatically. They are for services because when the service runs again, it sees the new options, but the daemon, which his already running, does not re-create its internal MySQL connection variable with the new MySQL options. You have to pt-agent --stop and pt-agent --daemonize again to get the daemon to use the new MySQL options.
Related branches
lp:~percona-toolkit-dev/percona-toolkit/pt-agent-fixes
- Daniel Nichter: Approve
-
Diff: 719 lines (+254/-147)4 files modifiedbin/pt-agent (+190/-144)
lib/Cxn.pm (+8/-1)
lib/Percona/Agent/Logger.pm (+2/-2)
t/lib/Cxn.t (+54/-0)
| summary: |
- pt-agent requires restart after chaning MySQL options + pt-agent requires restart after changing MySQL options |
| Changed in percona-toolkit: | |
| status: | Triaged → In Progress |
| Changed in percona-toolkit: | |
| status: | In Progress → Fix Committed |
| Changed in percona-toolkit: | |
| status: | Fix Committed → Fix Released |
Revision history for this message
| Shahriyar Rzayev (rzayev-sehriyar) wrote | #1 |
To post a comment you must log in.
Percona now uses JIRA for bug reports so this bug report is migrated to: https:/