replication timeout in pg_basebackup
| От | Aggarwal, Ajay |
|---|---|
| Тема | replication timeout in pg_basebackup |
| Дата | |
| Msg-id | 3B7431C850F4F347885C4CE5DD7B401993A93011@MIA20725MBX891A.apps.tmrk.corp обсуждение исходный текст |
| Ответы |
Re: replication timeout in pg_basebackup
Re: replication timeout in pg_basebackup |
| Список | pgsql-general |
Our environment: Postgres version 9.2.2 running on CentOS 6.4
Our backups using pg_basebackup are frequently failing with following error
Our replication timeout is default 60 seconds. If we increase the replication time to say 180 seconds, we see better results but backups still fail occasionally.
Running strace on pg_basebackup process, we see that the fsync() call takes significant time and could be responsible for causing this timeout in postgres.
Has anybody else run into the same issue? Is there a way to run pg_basebackup without fsync() ?
Our backups using pg_basebackup are frequently failing with following error
"pg_basebackup: could not send feedback packet: server closed the connection unexpectedly This probably means the server terminated abnormally before or while processing the request."In postgres logs we see this log message "terminating walsender process due to replication timeout".
We are invoking pg_basebackup with these arguments : pg_basebackup -D backup_dir -X stream -l backup_dir
Our replication timeout is default 60 seconds. If we increase the replication time to say 180 seconds, we see better results but backups still fail occasionally.
Running strace on pg_basebackup process, we see that the fsync() call takes significant time and could be responsible for causing this timeout in postgres.
Has anybody else run into the same issue? Is there a way to run pg_basebackup without fsync() ?
В списке pgsql-general по дате отправления: