Re: [Sqlgrey-users] sqlgrey fails when configured with multiple machines

[Jernej P. <jer...@ar...>]

On 01/07/14 11:21, Lionel Bouton wrote:
> Le 01/07/2014 10:59, Jernej Porenta a écrit :
>> Dear Alex,
>>
>> On 30/06/14 21:19, Alex wrote:
>>>   > We have successfully deployed sqlgrey with mysql master-slave
>>>   > configuration, where reads were performed into slave nodes, while SQL
>>>   > writes were done on the master node. After a while, we ditched sqlgrey
>>>   > in favour of posftwd2 and hapolicy...
>>>
>>> So did you ditch it for this reason? That sounds like how I have it set
>>> up here. Is it not possible to create a fault-tolerant sqlgrey system on
>>> its own?
>> I think that you would need a multi-master SQL setup to be able to use
>> sqlgrey in a way you are trying to set it up. The problem is that when
>> mysql master goes down, sqlgrey is unable to update database and it fails.
>
> It shouldn't. I didn't write the cluster support but with a single
> server, I coded SQLgrey to handle database failures gracefully and stop
> greylisting until the database server restarts.
> There's one exception : SQLgrey doesn't start correctly if the database
> server is unavailable, once it runs it should not fail.

Does "stop greylisting" means responding with DUNNO or does nor responds 
at all?

If it responds with DUNNO, then postfix continues working normally 
otherwise postfix issues an Server configuration error and defers a 
mail. This happens with all non-responsive policy servers...

I know that sqlgrey does great job at reconnecting to failing mysql 
servers, however I don't know the details behind it...

cheers, J.