On Tuesday 06 February 2007 3:47 pm, Andrew Sullivan wrote:
> On Tue, Feb 06, 2007 at 03:39:35PM -0600, Dan Falconer wrote:
> >     I'm confused.  It kinda sounds like you're saying "Slony isn't going to
> > work very well for me".  Previous to my upgrade to 1.2.6 (back in the
> > 1.1.0 days), Slony worked great for replicating,
>
> Hmm.  Well, if it _used_ to work for you, that's a different story.
> I think I must have misunderstood what you were saying, because I was
> under the impression you had this problem all along.
>
> Here's what the issue is, I think: once you get behind, catching up
> looks like it never happens, because a huge chunk of work all happens
> all in one giant transaction.  But it's also true that once you get
> very far behind, it's nearly impossible to catch up, because your
> inbound traffic is simply overwhelming Slony's ability to process
> both what's pending and what is coming in.
>
> As I said, my suggestion is to stop Slony, do some maintenance on the
> log tables and replicated tables (my bet is that Slony's replication
> process is getting the data via bad plans, because you've changed so
> much data), and then re-start.  Without seeing the slony logs and the
> like, it's pretty hard to guess, but that'd be my first blind one.
>
> A

        Well, I ran a vacuum analyze on the sl_log_2 table, and restarted the 
slon 
daemons... well, after doing that, and leaving it for over an hour, it seems 
to have caught-up by about 1 million transactions, but seems to be falling 
behind again (sl_log_2 now has 9.07M records, vs 10.3M), and growing again.

        I'm going to leave this overnight, and find out what happens, but I'm 
not 
very hopeful.  Tomorrow, if it hasn't caught up significantly, I'm going to 
have to do something drastic... and if 1.2.6 continues to drop behind so 
badly, I may have to (attempt to) revert backup to 1.1.0.  I may try just 
doing periodic restarts of the slon daemons, to see if that fixes the lag... 
but I'm praying that somebody will tell me about some magical shell script or 
setting to look for that'll get Slony back up to par, so I don't have to rip 
any more hair off the remnants of my scalp. :) 

-- 
Best Regards,


Dan Falconer
"Head Geek",
AvSupport, Inc. (http://www.partslogistics.com)
_______________________________________________
Slony1-general mailing list
[email protected]
http://gborg.postgresql.org/mailman/listinfo/slony1-general

Reply via email to