InnoDB: xtrabackup: Last MySQL binlog file position info printed twice while backup prepare
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Percona XtraBackup moved to https://jira.percona.com/projects/PXB | Status tracked in 2.4 | |||||
2.4 |
Confirmed
|
Low
|
Unassigned |
Bug Description
Running following command:
/home/shahriyar
InnoDB: Progress in percent: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
InnoDB: xtrabackup: Last MySQL binlog file position 7770684, file name mysql-bin.000003
InnoDB: xtrabackup: Last MySQL binlog file position 7770684, file name mysql-bin.000003
xtrabackup: starting shutdown with innodb_
InnoDB: Starting shutdown...
InnoDB: Shutdown completed; log sequence number 36252648
InnoDB: Number of pools: 1
171208 13:58:14 completed OK!
As you noticed:
"InnoDB: xtrabackup: Last MySQL binlog file position 7770684, file name mysql-bin.000003" is printed twice.
trx_sys_
But it is also called in:
if (recv_needed_
trx_
}
https:/
According to:
/** TRUE when recv_init_
extern bool recv_needed_
The crash recovery is done and recv_needed_
So maybe we can add a check if recv_needed_
The 2.3 version is not affected because there is no call of trx_sys_ print_mysql_ binlog_ offset( ) in srv0start.cc