Jan Wieck wrote:
> On 9/7/2007 9:36 AM, Cyril SCETBON wrote:
>> Hi,
>>
>> I got this configuration                Node1 --> Node2 (5 seconds late)
>>                                                           |
>>                                                           --> Node3 
>> (2 hours late)
>>
>> Node2 is processing each SYNC from Node3 and Node2, but Node3 is 
>> processing each SYNC from Node2 but not from Node1 which is the 
>> origin of the sets :
>>
>> On Node3 we see  `grep processing 
>> /var/log/slony1/node3-pns_profiles_preprod.log|awk '{print 
>> $5}'|sort|uniq -c`
>>      19 remoteWorkerThread_1:
>>     963 remoteWorkerThread_2:
>>
>> On Node2 we see `grep processing 
>> /var/log/slony1/node2-pns_profiles_preprod.log |awk '{print 
>> $5}'|sort|uniq -c`
>>    1570 remoteWorkerThread_1:
>>     865 remoteWorkerThread_3:
>>
>> Why is there so many SYNC not processed on Node3 ???
>>
>> Node3 got 22440 queue event and 25 Received event from 
>> remoteWorkerThread_1, while Node2 got 4467 queue event and 1578 
>> Received event from the same worker.
>>
>> Is there something to do ?
>
> How about looking for some error messages?
None.
>
> What comes to mind would be that sl_event is grossly out of shape and 
> that the event selection times out.
Seems vacuuming sl_log_1 takes too much time cause of vacuum_cost_delay 
and that selecting from this table use a seq scan. I'm investiguating.

Regards.
>
>
> Jan
>

-- 
Cyril SCETBON