pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Payal Singh <payal@omniti.com>
To: Henry Korszun <henryk302@yahoo.com>
Cc: Scott Whitney <swhitney@journyx.com>
Cc: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re:
Date: Fri, 25 Apr 2014 14:00:06 -0400
Message-ID: <20140425180005.GA6284@payal-ThinkPad-T520> (raw)
In-Reply-To: <1398448636.25048.YahooMailNeo@web162704.mail.bf1.yahoo.com>
References: <1398447433.8578.YahooMailNeo@web162701.mail.bf1.yahoo.com>
	<712112871.331097.1398447813672.JavaMail.zimbra@mail.int.journyx.com>
	<1398448636.25048.YahooMailNeo@web162704.mail.bf1.yahoo.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>

Once a trigger file is touched on slave, it makes the slave standalone, but doesn't stop the old primary server automatically. You have to handle that, by either stopping the old primary altogether or pointing a virtual ip to the new slave. 
On Fri, Apr 25, 2014 at 10:57:16AM -0700, Henry Korszun wrote:
> There IS a trigger file, which does appear to have been "touch"ed.  But the problem is that a fail-over hasn't really occurred since the original read/write primary continues to be a fully functioning read/write machine. But it's no longer replicating to the erstwhile standby, which has become read/write.  Bottom line, I now have 2 read/write machines, but with no replication between them.
> 
> On Friday, April 25, 2014 1:43 PM, Scott Whitney <scott@journyx.com> wrote:
>  
> Sounds like you might have a "trigger_file" set in your recovery.conf. Do you? That or someone is issuing a pg_ctl promote command.
> 
> ________________________________
> 
> I'm using PostgreSQL 9.2.4 on x86_64-unknown-linux-gnu, compiled by gcc (GCC) 4.1.2 20070115 (SUSE Linux), 64-bit.
> >
> >I set up streaming replication for a read/write primary and a read/only 
> standby.  The replication works fine for a while, and then out of the 
> blue BOTH machines become read/write, but with no replication from the 
> original primary to the newly read/write standby. 
> >
> >The only log entry that seems relevant is as follows: 
> FATAL,57P01,"terminating walreceiver process due to administrator 
> command",,,,,,,,"ProcessWalRcvInterrupts, walreceiver.c:150",""
> >
> >Any help/guidance would be appreciated. Thanks in advance. 
> >
> >


-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin



view thread (11+ messages)  latest in thread

Message-ID: <20140425180005.GA6284@payal-ThinkPad-T520>
Permalink:  ../20140425180005.GA6284@payal-ThinkPad-T520/
Also on:    postgresql.org/message-id/20140425180005.GA6284@payal-ThinkPad-T520

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: payal@omniti.com, henryk302@yahoo.com, swhitney@journyx.com
  Subject: Re:
  In-Reply-To: <20140425180005.GA6284@payal-ThinkPad-T520>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox