pt-online-schema-change will proceed even if no slaves are connectable, rendering throttling useless
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona Toolkit moved to https://jira.percona.com/projects/PT |
Invalid
|
Undecided
|
Unassigned |
Bug Description
1) run pt-osc with a user who has permissions to the master but not the slaves
2) notice many errors like : print STDERR "Cannot connect to ", $dp->as_
3) even if 100% of slaves fail, pt-online-
4) users typically expect throttling to work when it is enabled by default
I suggest making it FATAL when you can discover slaves but are unable to monitor a single one, and require that the user set --recursion-
tags: | added: privs pt-online-schema-change |
Changed in percona-toolkit: | |
status: | New → Triaged |
This is an oldie, so some things have changed back and forth since. method= dsn , where you can tell the tool exactly which slaves to monitor, (using different user/passwords if necessary)
Current behavior (v2.2.15) is to not exit when a slave is unreachable. This is desirable when you have a very long run (hours/days) with various slaves and at some point you want to take one offline (for whatever reason), but don't want tool to exit and lose all the work done.
I think the situation described in the report can be handled with --recursion-
See: /www.percona. com/doc/ percona- toolkit/ 2.2/pt- online- schema- change. html#cmdoption- pt-online- schema- change- -recursion- method
https:/