[CTDB] strange fork bomb bug

[Mathieu Parent]

2015-07-24 13:08 GMT+02:00 Martin Schwenke <martin at meltin.net>:
> Waiting for a compile, so going back through some of my backlog.  I
> don't suppose this answer will be useful anymore, but I feel like
> answering anyway...  :-)

Thanks anyway ;-)

> On Wed, 26 Mar 2014 15:53:33 +0100, Mathieu Parent
[...]
>
>   2014/03/02 06:46:54.815240 [recoverd: 3960]: server/ctdb_recoverd.c:3427 Remote node:0 has different flags for node 4. It has 0x01 vs our 0x00
>   2014/03/02 06:46:54.815276 [recoverd: 3960]: Use flags 0x00 from local recmaster node for cluster update of node 4 flags
>
> For some reason it looks like node 0 can't see node 4 but other nodes
> can.  If node 0 keeps getting it wrong then it should be banned.
> Perhaps this is fixed by now?  ;-)
>
> This also points to the fact that doing a database recovery won't help
> fix inconsistent node flags across the cluster.  It just so happens
> that we push flags out across the cluster in the recovery code.
> However, they're 2 separate problems: flags are cluster management,
> recovery is database.  That will be improved in the long term...

Good.

I didn't had the problem since month. We may have fixed something but
I don't know what :-P

Regards

-- 
Mathieu