Re: Need assistance for replication sync issue

Поиск

Список

Период

Сортировка

От	Tomek
Тема	Re: Need assistance for replication sync issue
Дата	23 октября 2023 г. 14:58:58
Msg-id	CACUaW3Tdpnx4kJFG52CWs4O+r6JbTo_8+vhKOG1xoyuBVvV_pg@mail.gmail.com обсуждение исходный текст
Ответ на	Re: Need assistance for replication sync issue (Veerendra Pulapa <veerendra.pulapa@ashnik.com>)
Список	pgsql-admin

Дерево обсуждения

  As understanded you have DR for backup purposes only.
I think you should not use stream replication to the DR - use only sending of WALs. Definitely you will have lag but it is better to have a lag than break and a need to make pg_dumpall from the beginning.  

pt., 20 paź 2023 o 06:17 Veerendra Pulapa <veerendra.pulapa@ashnik.com> napisał(a):

Dears,

Thank you all for your response. Below are the general details about our setup.

Our setup is DC & DR.
On DC: Three nodes(one master, Two replicas) and replication mode is asynchronous between DC.
On DR: One replica and replication mode is asynchronous between DC & DR.
All four nodes have the same configuration such as CPU,RAM and Disks.
In DC no replication & in DR yes it's always replication lag due to this our replication got broken.
The setup runs on on-prem RHEL 7.9 and PG 12.x.

Is there a way to perform an incremental data restore if replication breaks at a certain point? The data size is substantial, and when replication breaks between the DC and DR, it takes 3 to 4 days to rebuild the replica.

Br,
Veerendra Pulapa | Technical Consultant
M: +91-9949349894 | www.ashnik.com

On Thu, Oct 19, 2023 at 7:23 PM Jwiencek3 <jwiencek3@comcast.net> wrote:
Look at using synchronous replication.

Sent from my iPad

On Oct 19, 2023, at 5:38 AM, Licio Matos <licio.matos@gmail.com> wrote:

Hi Veerendra,

Is your servers, primary and secondary, the same size? CPU, Memory etc.

Licio Matos

Em qui., 19 de out. de 2023 às 07:12, Veerendra Pulapa <veerendra.pulapa@ashnik.com> escreveu:
Hello,

I need some help with a database issue we’re facing. We have a situation where our primary data center and our disaster recovery site are far apart, and this long distance is causing delays in keeping our data synchronized. It’s become a problem as we want our data to be as up-to-date as possible.

Do you have any suggestions for dealing with this kind of situation? We’ve tried a few things, but we’re still struggling with the replication delays caused by the high latency between the sites.

Note: Bandwidth is very low and latency is very high.

I’d appreciate any advice you can provide.

Thanks in advance.

Get Outlook for iOS