Tue Nov 23 00:05:34 PST 2010
- Previous message: [Slony1-general] Slonik Awareness of Cluster State (was Automatic WAIT FOR EVENT)
- Next message: [Slony1-general] Slonik Awareness of Cluster State
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Fri, Nov 19, 2010 at 9:44 PM, Vick Khera <vivek at khera.org> wrote: > On Fri, Nov 19, 2010 at 4:28 AM, Stuart Bishop <stuart at stuartbishop.net> wrote: >>> That suggests to me there being some value to having some sort of "fail >>> if not sufficiently up to date" command. >> >> Pretty much all my canned scripts start by issuing a sync and waiting >> for it. I think it is dangerous to do otherwise. Failing with a >> meaningful error rather than leaving sysadmins staring at a blinking >> prompt would be preferable. > > Nice. What does this look like in the script? echo 'Waiting for cluster to sync. If this blocks, check for long running transactions and working slon daemons.'; SYNC (id=@master_node); WAIT FOR EVENT (origin=@master_node, wait on=@master_node, confirmed=ALL); echo 'Synced.'; -- Stuart Bishop <stuart at stuartbishop.net> http://www.stuartbishop.net/
- Previous message: [Slony1-general] Slonik Awareness of Cluster State (was Automatic WAIT FOR EVENT)
- Next message: [Slony1-general] Slonik Awareness of Cluster State
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list