pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Alex Ignatov <a.ignatov@postgrespro.ru>
To: HEMPLEMAN Matthew <matthew.hempleman@alstom.com>
To: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: Replication Cluster Monitoring
Date: Fri, 7 Aug 2015 18:25:33 +0300
Message-ID: <55C4CDED.9070607@postgrespro.ru> (raw)
In-Reply-To: <AE4EB74F2AE1C34FB54435AD9878F63652743C@041-DB3MPN1-027.041d.mgd.msft.net>
References: <AE4EB74F2AE1C34FB54435AD9878F63652743C@041-DB3MPN1-027.041d.mgd.msft.net>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>

On 07.08.2015 3:12, HEMPLEMAN Matthew wrote:
>
> Hi All,
>
> Please bear with me as I’m not a dba and I’m new to Postgres.  I’m 
> writing a Java application to monitor a streaming replication cluster 
> (Windows).  I want to monitor the Master and initiate failover if 
> necessary (something like a scaled down version of pgpool).  I also 
> want to monitor the standby and terminate synchronous replication in 
> the event of a failure.  At this point, my app is polling the Master 
> every N seconds and triggering a failover if the wait is too long or 
> it receives a connection error.  I’m worried that this method of 
> assessing server health could lead to false-failovers.  Any 
> suggestions as to specific health checks I could run or issues I 
> should watch out for?  Thanks!
>
>
> ------------------------------------------------------------------------
> CONFIDENTIALITY : This e-mail and any attachments are confidential and 
> may be privileged. If you are not a named recipient, please notify the 
> sender immediately and do not disclose the contents to another person, 
> use it for any purpose or store or copy the information in any medium.

I think you should follow this way:
http://clusterlabs.org/wiki/PgSQL_Replicated_Cluster

-- 
Alex Ignatov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company



---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

view thread (3+ messages)  latest in thread

Message-ID: <55C4CDED.9070607@postgrespro.ru>
Permalink:  ../55C4CDED.9070607@postgrespro.ru/
Also on:    postgresql.org/message-id/55C4CDED.9070607@postgrespro.ru

 · 

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: a.ignatov@postgrespro.ru, matthew.hempleman@alstom.com
  Subject: Re: Replication Cluster Monitoring
  In-Reply-To: <55C4CDED.9070607@postgrespro.ru>

* 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