| From: | Rui DeSousa <rui(at)crazybean(dot)net> |
|---|---|
| To: | Mariel Cherkassky <mariel(dot)cherkassky(at)gmail(dot)com> |
| Cc: | repmgr(at)googlegroups(dot)com, pgsql-admin(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Investigate postgres 9.6.3 repmgr lag 4.0.4 |
| Date: | 2018-06-24 15:32:37 |
| Message-ID: | A86CBFD8-B27C-409C-8332-C73B84FD3153@crazybean.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
> On Jun 24, 2018, at 4:59 AM, Mariel Cherkassky <mariel(dot)cherkassky(at)gmail(dot)com> wrote:
>
>
> Now, How can I further investigate it ? my wal_keep_segment is assigned to 100 but since friday 261 wals were generated so I guess I dont have another option but to sync the node again. However, I want to understand why it happened. What can you advice me to check ?
>
What is the connectivity between the nodes, any firewalls? What’s the settings for wal_sender_timeout and wal_receiver_timeout? Why not use a replication slot or have it fail over to using the archived WALs instead of full database restore?
There should be other messages in Postgresql logs.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Flavio Henrique Araque Gurgel | 2018-06-24 16:22:50 | Re: Investigate postgres 9.6.3 repmgr lag 4.0.4 |
| Previous Message | Mariel Cherkassky | 2018-06-24 08:59:31 | Investigate postgres 9.6.3 repmgr lag 4.0.4 |