High Availability Cluster

Maila Fatticcioni <mfatticcioni@mbigroup.it> wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello.
I need to set up a high availability cluster with two servers. I have
looked for the best configuration I could use but I cannot find
anything I like. I cannot used the DRBD option and I have to use

I was wondering if there is another way to set up a complete cluster
that would manage in case of failure:

* the relocation of the VIP (virtual ip address)
* the relocation of the main instance of Postgresql

Best Regards,
Maila Fatticcioni

Why not DRBD & Pacemaker?

Andreas
--
Really, I'm not out to destroy Microsoft. That will just be a completely
unintentional side effect. (Linus Torvalds)
"If I was god, I would recompile penguin with --enable-fly." (unknown)
Kaufbach, Saxony, Germany, Europe. N 51.05082�, E 13.56889�

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

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 11/27/2014 12:34 PM, Andreas Kretschmer wrote:

Maila Fatticcioni <mfatticcioni@mbigroup.it> wrote:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

Hello. I need to set up a high availability cluster with two
servers. I have looked for the best configuration I could use but
I cannot find anything I like. I cannot used the DRBD option and
I have to use

I was wondering if there is another way to set up a complete
cluster that would manage in case of failure:

* the relocation of the VIP (virtual ip address) * the relocation
of the main instance of Postgresql

Best Regards, Maila Fatticcioni

Why not DRBD & Pacemaker?

Andreas

We would prefer to not use DRBD to speed up the performance.
Is there any other available solution?

Maila

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iEYEARECAAYFAlR3UlMACgkQi2q3wPb3FcNA9gCfd/veNBuNkmPSIbjdkHqeRdgK
CDMAoLul8+oO6CI9L9/7uCMlblLab9qP
=9OrT
-----END PGP SIGNATURE-----

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

On Thu, Nov 27, 2014 at 7:26 PM, Maila Fatticcioni <mfatticcioni@mbigroup.it

wrote:

I was wondering if there is another way to set up a complete cluster
that would manage in case of failure:

* the relocation of the VIP (virtual ip address)
* the relocation of the main instance of Postgresql

​Consider trying pgpool. It has an HA mode (and I think the latest version
works using a heartbeat, the older one uses watchdog).

If you are up for a commercial product, you may want to consider using
something like EnterpriseDB's failover manager.
​

Best Regards,

*Sameer Kumar | Database Consultant*

*ASHNIK PTE. LTD.*

101 Cecil Street, #11-11 Tong Eng Building, Singapore 069533

M: *+65 8110 0350* T: +65 6438 3504 | www.ashnik.com

*[image: icons]*

[image: Email patch] <http://www.ashnik.com/&gt;

This email may contain confidential, privileged or copyright material and
is solely for the use of the intended recipient(s).

On Thu, Nov 27, 2014 at 7:26 PM, Maila Fatticcioni <mfatticcioni@mbigroup.it

wrote:

I was wondering if there is another way to set up a complete cluster
that would manage in case of failure:

* the relocation of the VIP (virtual ip address)
* the relocation of the main instance of Postgresql

​Consider trying pgpool. It has an HA mode (and I think the latest version
works using a heartbeat, the older one uses watchdog).

No. Just the implementation of watchdog has been changed (more
precisely new life check mode added). In recent versions (since 3.3)
it uses UDP packet for life check of pgpool, which is pretty much
similar to heartbeat.

If you are up for a commercial product, you may want to consider using
something like EnterpriseDB's failover manager.

Commercial support for pgpool-II is provided by the way.

Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp

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

On Thu, Dec 4, 2014 at 12:32 PM, Tatsuo Ishii <ishii@postgresql.org> wrote:

No. Just the implementation of watchdog has been changed (more
precisely new life check mode added). In recent versions (since 3.3)
it uses UDP packet for life check of pgpool, which is pretty much
similar to heartbeat.

​Thanks for adding the details.

​

If you are up for a commercial product, you may want to consider using
something like EnterpriseDB's failover manager.

Commercial support for pgpool-II is provided by the way.

​
Noted :)​

Best Regards,

*Sameer Kumar | Database Consultant*

*ASHNIK PTE. LTD.*

101 Cecil Street, #11-11 Tong Eng Building, Singapore 069533

M: *+65 8110 0350* T: +65 6438 3504 | www.ashnik.com

*[image: icons]*

[image: Email patch] <http://www.ashnik.com/&gt;

This email may contain confidential, privileged or copyright material and
is solely for the use of the intended recipient(s).