delete binlogs when clone nodes
Bug #519832 reported by
ufaria
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
mysql-mmm |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
I have a mysql instalation that has master logs in its own directory because i don't want
to share same logical volume for data and master logs. The directory that i clone and copy
with mmm is only the datadir of mysql but when it finish can't delete the master log because is
in other directory and then reconnect the peer with old master log that where in the node before
the clone.
is good practice to separate masterlog, slavelog and data ?
can i specify the masterlog directory on the mmm conf?
and for slavelog?
why mmm_clone copy masterlogs and binarylogs to inmediately delete them?
thx.
Changed in mysql-mmm: | |
status: | New → Confirmed |
To post a comment you must log in.
> can i specify the masterlog directory on the mmm conf?
No, not if its on a different LV.
> why mmm_clone copy masterlogs and binarylogs to inmediately delete them?
the mmm-tools expect everything (data/logs) to be on the same LV: they can't do snapshots of multiple LVs at the moment + mmm_backup is design to also create a backup of the binlogs. (mmm_clone is basically a mmm_backup combined with mmm_restore)