Check privileges on backup start
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Percona XtraBackup moved to https://jira.percona.com/projects/PXB | Status tracked in 2.4 | |||||
2.0 |
Won't Fix
|
Medium
|
Unassigned | |||
2.1 |
Won't Fix
|
Medium
|
Unassigned | |||
2.2 |
Won't Fix
|
Medium
|
Unassigned | |||
2.3 |
Fix Released
|
Medium
|
Vasily Nemkov | |||
2.4 |
Fix Released
|
Medium
|
Vasily Nemkov |
Bug Description
XtraBackup documentation provides information on connection privileges required by innobackupex depending on options: http://
The problem is that innobackupex does not check those privileges on startup. The only thing it checks is whether it is able to connect to the server. If that works, it then proceeds to copy InnoDB tables.
Which means it can take hours after starting a backup and before a user can discover innobackupex does not have sufficient privileges to execute FTWRL or start/stop the slave thread, etc., or there's a typo in credentials.
Checking the privileges on backup start and aborting would be a nice usability improvement.
PR: https:/ /github. com/percona/ percona- xtrabackup/ pull/372