From: | "Aggarwal, Ajay" <aaggarwal(at)verizon(dot)com> |
---|---|
To: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | replication timeout in pg_basebackup |
Date: | 2014-03-10 01:52:33 |
Message-ID: | 3B7431C850F4F347885C4CE5DD7B401993A93011@MIA20725MBX891A.apps.tmrk.corp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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
"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."
We are invoking pg_basebackup with these arguments : pg_basebackup -D backup_dir -X stream -l backup_dir
In postgres logs we see this log message "terminating walsender process due to replication timeout".
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() ?
From | Date | Subject | |
---|---|---|---|
Next Message | Haribabu Kommi | 2014-03-10 05:42:18 | Re: replication timeout in pg_basebackup |
Previous Message | Yngve N. Pettersen | 2014-03-10 01:41:44 | Re: Possible multiprocess lock/unlock-loop problem in Postgresql 9.2 |