Craig James <craig_james at emolecules.com> writes:
> Ow Mun Heng wrote:
>> I came to work today and seems like the slave server died. (power trip?
>> No it was not connected to a UPS :-()
>> I've not been able to locate/determine if the slave is really dead or
>> otherwise and it's the weekend in Asia and there's no one in the office
>> till Next week.
>> As of now, the master is still trying to contact the slave (slon is
>> still running on the master) and log_1 and log_2 is filling up.
>> And yesterday, I just created a job to manually force the log_switch
>> to
>> occur. So, right now, I'm at a loss as to what i can do.
>
> Just kill all of the Slony daemons.  Next week when the other server
> is back, start them again.  It will figure out what it missed, and
> will catch up with no problems.

That's not quite accurate...

If you kill ALL the daemons, and don't have *something* maintaining
the creation of SYNCs (e.g. - a script running the "generate_sync()"
stored function), then there will be one really gigantic SYNC covering
the interval of [time slon for origin died] until [time slon for
origin restarted].

It might well be a good answer to set up an every-minute or
every-few-minutes script that runs against the origin and runs the
"generate_sync()" stored function.  There's not much value in lower
intervals than that.  And that's about all the maintenance that is of
value between now and next week.

So I would suggest one of two choices:

a) Set up generate_sync() cron job, and kill all slons.

b) Increase the various sync parms for the slon for the origin node;
-s 60000 and -t 120000 will mean you SYNC once per minute, when things
are busy.

That reduces the work level a bit., either way.
-- 
let name="cbbrowne" and tld="linuxfinances.info" in name ^ "@" ^ tld;;
http://www3.sympatico.ca/cbbrowne/sgml.html
If you eat a live  frog in the morning, nothing  worse will happen  to
either of you for the rest of the day.