Re: Replication failed after stalling

Поиск
Список
Период
Сортировка
От Joe Van Dyk
Тема Re: Replication failed after stalling
Дата
Msg-id CACfv+pK1xSqKEEMURvBLRYaBVBY0wsNpTYffMWq=R9Cf_FLrFg@mail.gmail.com
обсуждение исходный текст
Ответ на Replication failed after stalling  (Joe Van Dyk <joe@tanga.com>)
Ответы Re: Replication failed after stalling
Список pgsql-general
Дерево обсуждения
A possibly related question:

I've set wal_keep_segments to 10,000 and also have archive_command running wal-e. I'm seeing my wal files disappear from pg_xlog after 30 minutes. Is that expected? Is there a way around that?

(I want to use streaming replication and wal-e for PITR restores)


On Wed, Dec 18, 2013 at 11:26 AM, Joe Van Dyk <joe@tanga.com> wrote:
I'm running Postgresql 9.3. I have a streaming replication server. Someone was running a long COPY query (8 hours) on the standby which halted replication. The replication stopped at 3:30 am. I canceled the long-running query at 9:30 am and replication data started catching up.

The data up until 10 am got restored fine (took until 10:30 am to restore that much). Then I started getting errors like "FATAL:  could not receive data from WAL stream: ERROR:  requested WAL segment 00000001000003C300000086 has already been removed".

I'm confused about how pg could restore data from 3:30 am to 10 am, then start complaining about missing WAL files.

What's the best way to avoid this problem? Increase wal_keep_segments?

Joe

В списке pgsql-general по дате отправления:

Предыдущее
От: John R Pierce
Дата:
Сообщение: Re: Multi Master Replication
Следующее
От: Jerry Sievers
Дата:
Сообщение: Re: Replication failed after stalling