[pgpool-general: 8029] Re: Pgpool HA in AWS

RAJAMOHAN garajamohan at gmail.com
Tue Mar 1 14:36:18 JST 2022


On Tue, Mar 1, 2022 at 7:20 AM Bo Peng <pengbo at sraoss.co.jp> wrote:

> Hello,
>
> On Thu, 24 Feb 2022 15:15:34 +0530
> RAJAMOHAN <garajamohan at gmail.com> wrote:
>
> > Hello team,
> >
> > I am setting up a high availability architecture for pgpool using ec2
> > instances. I am able to complete 2 node pgpool instances setup in the
> same
> > subnet using watchdog by detaching and attaching secondary ENI (Private
> > ip). And it's working fine.
> >
> > As a next step I am planning to setup two pgpool instances in 2 different
> > availability zones to avoid AZ level outages as well. But the problem now
> > is since both AZ's have different subnet ranges I can't use the secondary
> > ENI or elastic ip approach.
> >
> > Are there any other options to overcome this? Any suggestions or ideas
> will
> > be helpful?
>
> If you are using different AZ, there two ways to setup VIP:
>
>   1. rewrite route table (It's required to disable source-destination
> check)
>   2. Route53
>
> Below is a slide in Japanese(p.41-46), I hope it can be helpful.
>
>
> https://www.sraoss.co.jp/wp-content/uploads/files/event_seminar/material/2017/jpug_20171103_pgpool_aws.pdf
>
>
>
Thanks Bo Peng.

Route53 really simplified the task.



Thanks & Regards,
Rajamohan.J
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pgpool.net/pipermail/pgpool-general/attachments/20220301/2acc5490/attachment.htm>


More information about the pgpool-general mailing list