On 8/28/07, Dan Falconer <lists_slony1-general at avsupport.com> wrote:
> Slony is now 6+ days behind on the slave server.  I just upped the max sync
> group size from 25 to 500.  I am hoping that has some significant impact, as
> soon I'm going to have to go through the process of dropping schema and
> re-initializing the whole thing.
>
> For what it's worth, it seems to me that the failed log switch has a lot to do
> with the problem.  I mean, Slony is retrieving all of the events, as the
> slave's log files are fairly massive (sl_log_1=413981, sl_log_2=3935888)...
> or something.  I'm very confused as to where things are breaking down, and I
> just don't know what to look for anymore.  SYNCs are processing, seeming to
> indicate that it's TRYING to work... if somebody could shed light on what to
> look for in the logs, that would be great.

Hi Dan, we've already said what the problem is - While SYNCs are
processing, they are taking way too long to keep up with the current
rate of change.

Have you been able to up the debug level to 4 and grab a log snippet
from the slave after bumping up the sync group size?

Have you also tried stopping the slon daemons and doing a vacuum
analyze on the sl_log tables again to see if that speeds up SYNC
processing?

Have you also verified that there are no long running transactions on
the master?

-Dave