Extended replication variable capture
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
Extend and improve the capture of replication variables in three ways:
1. Correct innobackupex to get the file and position from the last executed SQL statement rather than the last statement read by the IO thread:
Master_Log_File should be changed to Relay_Master_
Master_Log_Pos should be changed to Exec_Master_Log_Pos for clarity -- this is actually already the variable that is matched due to the order of the output of SHOW SLAVE STATUS, which prints:
[...]
both of which are matched by /Master_
2. Add (perhaps optionally) specific master host connectivity variables to xtrabackup_
We know MASTER_HOST and MASTER_USER, and can output them. This may not always be desirable, but is useful when cloning an existing slave to make another slave. My included patch doesn't wrap them in a command line flag option, but it could be added.
MASTER_PASSWORD is also added, but blank, since we can't get it.
3. Capture relay log and position
Add Relay_Log_File, Relay_Log_Pos in a comment in xtrabackup_
Changed in percona-xtrabackup: | |
importance: | Undecided → High |
tags: | added: replication |
tags: | added: innobackupex |
Changed in percona-xtrabackup: | |
assignee: | nobody → Valentine Gostev (longbow) |
Changed in percona-xtrabackup: | |
assignee: | Valentine Gostev (longbow) → nobody |
tags: | added: contribution |
Note that /Master_ Log_File: \s*(\S* )\s*$/ will match Relay_Master_ Log_File and do the right thing because of the order of SHOW SLAVE STATUS (just like Master_Log_Pos), but I still feel it should be changed for clarity.