Re: Cascade Standby - HELP!
| От | Murthy Nunna |
|---|---|
| Тема | Re: Cascade Standby - HELP! |
| Дата | |
| Msg-id | BD7563973EF8894D905C80593EE9A4ED35CC54@MAIL01.fnal.gov обсуждение исходный текст |
| Ответ на | Re: Cascade Standby - HELP! (Scott Whitney <scott@journyx.com>) |
| Список | pgsql-admin |
Hi Scott,
Yes, I thought of increasing wal_keep_segments but it doesn’t seem to be a bullet proof solution. It locks that much space and most of the time it is a wasted space since streaming will be working and you really don’t need these logs hanging around.
Besides, things work fine in primary->slave configuration because archive_command ships the logs constantly to slave and if slave is in good hands of streaming it cleans up the logs. It will use it only when it is necessary for gap resolution. However, it doesn’t work from slave->slave configuration because the archive_command has no meaning there while it is recovery mode and it has no logs of its own.
This restriction limits the cascade feature and makes it fragile in my opinion. It could break anytime and you end up rebuilding.
Thanks,
Murthy
From: pgsql-admin-owner@postgresql.org [mailto:pgsql-admin-owner@postgresql.org] On Behalf Of Scott Whitney
Sent: Wednesday, April 02, 2014 3:49 PM
To: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] Cascade Standby - HELP!
My only response that might help you with this is that my setup is:
Server 1) primary production db server (5432)
Server 2) replicates production (5432) also primary for non-production use (6432)
Server 3) (offsite) replicates #2 (5432 -> 7432 internally and 6432 -> 6432) AND hosts internal databases
So:
1) Production
2) Replication + non production
3) Internal + replication of NON production + replication of PRODUCTION (via the cascaded server)
I would find that when replicating the PRODUCTION server internally (#3), I had not set wal_keep_segments high enough,
due to the lag of WAN replication, production and non production would replicate fine (gigabit backend), but sometimes when
a load of data was being updated/moved/deleted, the offsite (#3) would fall behind far enough that it could not recover
without a new pg base backup, in essence setting up replication again.
I solved this by upping the wal_keep_segments.
Hi Robert,
Thanks for the response. Mine is 9.2.4 and the issue is specifically with cascading standby. I don’t think 8.3 had that feature.
Murthy
From: pgsql-admin-owner@postgresql.org [mailto:pgsql-admin-owner@postgresql.org] On Behalf Of Burgholzer, Robert (DEQ)
Sent: Wednesday, April 02, 2014 3:29 PM
To: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] Cascade Standby - HELP!
Murthy,
I have experienced something similar to this issue, and recall that it had to do with log file difficulties. I tried my best to document this, but recall that I had problems working back through it, so please, note that this is a procedure that carries no guarantees. Note that the step-by-step calls a couple of custom scripts that I wrote (they are at the end of the page), AND this is on an 8.3 postgresql install:
Regards,
/r/b
В списке pgsql-admin по дате отправления:
Следующее
От: Matthew RantalaДата:
Сообщение: How to find calculated CRC checksum of pg_controldata