Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1ZNjWh-0007Fs-B0 for pgsql-admin@arkaria.postgresql.org; Fri, 07 Aug 2015 15:25:43 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84) (envelope-from ) id 1ZNjWg-0004r4-Br for pgsql-admin@arkaria.postgresql.org; Fri, 07 Aug 2015 15:25:42 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84) (envelope-from ) id 1ZNjWf-0004qp-KL for pgsql-admin@postgresql.org; Fri, 07 Aug 2015 15:25:41 +0000 Received: from newmail.postgrespro.ru ([93.174.131.138] helo=mail.postgrespro.ru) by makus.postgresql.org with esmtp (Exim 4.84) (envelope-from ) id 1ZNjWc-00047r-4e for pgsql-admin@postgresql.org; Fri, 07 Aug 2015 15:25:40 +0000 Received: from [127.0.0.1] (unknown [192.168.27.1]) by mail.postgrespro.ru (Postfix) with ESMTPSA id 96AB421C2626; Fri, 7 Aug 2015 18:25:35 +0300 (MSK) Subject: Re: Replication Cluster Monitoring To: HEMPLEMAN Matthew , "pgsql-admin@postgresql.org" References: From: Alex Ignatov Message-ID: <55C4CDED.9070607@postgrespro.ru> Date: Fri, 7 Aug 2015 18:25:33 +0300 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.1.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/alternative; boundary="------------060603020001030603090305" X-Antivirus: avast! (VPS 150807-0, 07.08.2015), Outbound message X-Antivirus-Status: Clean X-Pg-Spam-Score: -2.0 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org This is a multi-part message in MIME format. --------------060603020001030603090305 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit 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 --------------060603020001030603090305 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: 8bit 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


Avast logo

This email has been checked for viruses by Avast antivirus software.
www.avast.com


--------------060603020001030603090305--