From: | HEMPLEMAN Matthew <matthew(dot)hempleman(at)alstom(dot)com> |
---|---|
To: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Replication Cluster Monitoring |
Date: | 2015-08-07 00:12:07 |
Message-ID: | AE4EB74F2AE1C34FB54435AD9878F63652743C@041-DB3MPN1-027.041d.mgd.msft.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
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.
From | Date | Subject | |
---|---|---|---|
Next Message | James Sebastian | 2015-08-07 09:07:05 | Re: Postgres 9.1 - getting a continous archiving database to accept connections taking too long |
Previous Message | John Scalia | 2015-08-06 21:00:24 | Re: pg_basebackup problem... |