xtrabackup_slave_info can be misleading
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona XtraBackup moved to https://jira.percona.com/projects/PXB |
Triaged
|
Wishlist
|
Unassigned | ||
2.1 |
Triaged
|
Wishlist
|
Unassigned | ||
2.2 |
Triaged
|
Wishlist
|
Unassigned | ||
2.3 |
Triaged
|
Wishlist
|
Unassigned |
Bug Description
Maybe i'm splitting hairs, but I feel the filename xtrabackup_
When the slave ( where the backup was taken ) and the master are on the same binlog #, you can easily get confused.
Maybe renaming xtrabackup_
Getting the correct logging position ( atleast in 5.5 without GTIDs ) is one of the most important steps so you dont lose transactions. Having to do this mental conversion of file names isn't helpful.
Just my .02
Agree, most metadata filenames are misleading. We can target fixing this for the next major release, i.e. 2.1.