[chef] Re: *** PROBABLY SPAM *** {Spam?} Re: Mysql active/active cluster cookbook

[Tensibai < >]

On Fri, 4 Nov 2011 23:06:59 +0100, Jochen Lillich wrote:

> On Thu, Nov 3, 2011 at 3:28 PM, Tensibai wrote:
>
> > I'm looking for a work base to check sync of an active/active mysql
> > cluster and redo the sync in case one of the node is unsync.
> Hi Tensibai, am I correct in understanding that you'd like a recipe
> that rebuilds a MySQL master-master replication after failing? That
> doesn't look like a trivial task because you'd need to have the two
nodes
> exchange data and status while rebuilding (e.g., lock the database on
one
> node while setting the new replication start point on the other).
>
> (And I'm not sure if I'd want this kind of self-healing in the first
> place, but that's another discussion.) Best regards, Jochen

HI Jochen,

You're correct on the understanding, and I agree the repair should not 
be automatic.
I'm more thinking about a node attribute 'need_resync_db' I would set 
to the DB needed resync once verified which node is out of sync.

For the consistency check I though about a recipe using maatkit to 
check consistency and alerting/listing when there's a problem and a 
recipe doing the resync (lock, dump, reload) and reseting the node 
attribute once done.

I just wonder if there's something already existing or if I should 
write it on my own.
As I'm really new to chef I try not to reinvent the wheel and I'm 
pretty sure I don't know some helpfull cookbook sources :)

Thanks for your answer

Tensibai