On 04/19/2011 10:20 AM, Marek Marczykowski wrote: > On 04/19/11 10:01, Raoul Bhatia [IPAX] wrote: >> what i can currently think of: >> >> 1. run a cronjob which periodically analyzes the binlogs and will update >> the node's log-file and log-pos attributes if there are empty binlogs; >> (that's the best method, i think) >> >> 2. restore the purged binlogs from a backup, hack the mysql-bin.index >> file to re-include them, and hope that they will not be purged upon >> replication restart? >> >> >> any input on this? > > I've similar problem... I think the first solution is better - after 7 > days log-file and log-pos can be cleared to use "FIRST" as start point.
in your opintion, is it possible to fix this via the ocf ra or does it have to be a separate cronjob? thanks, raoul -- ____________________________________________________________________ DI (FH) Raoul Bhatia M.Sc. email. r.bha...@ipax.at Technischer Leiter IPAX - Aloy Bhatia Hava OG web. http://www.ipax.at Barawitzkagasse 10/2/2/11 email. off...@ipax.at 1190 Wien tel. +43 1 3670030 FN 277995t HG Wien fax. +43 1 3670030 15 ____________________________________________________________________ _______________________________________________ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
