PostgreSQL Automatic Fail-over in On-Premise instance
We have upgraded Pega CoBrowse from 7.22.5 to 7.31 on On premise, Upgraded Node, Configured the config.json and made to work with PostgreSQL in Non-HA environment.
For HA, We setup replication in PostgreSQL with 1 Master and 1 Standby node and tested successfully. For Automatic failover, we checked on different forums and found that there is a manual intervention needed whenever master goes down. After the master is bought back to normal condition, manual intervention is needed to sync the data from new master to it.
Can you please provide information on the below points:
1. Third party tools to setup automatic failover for PostgreSQL database without manual activity?
2. How to configure the connection string in Config.json of CoBrowse to support the automatic failover of PostgreSQL?
As of now , we don’t support automatic failover for Postgres, We rely on infrastructure where DNS entries updated with master node . I.e. You need to switch the DNS entries for the current active DB node.
Co-Browse configuration allows you to configure only one Postgres entry which is master.