This repository has been archived by the owner on Jan 18, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 223
pgbackrest container can't start when running on slave pod #83
Labels
bug
Something isn't working
Comments
feikesteenbergen
added a commit
that referenced
this issue
Jan 17, 2020
The check command of pgBackRest used to succeed on the replica, but this behaviour changed recently [1] and will be ok in the long term. This commit is a workaround for this change, and will only check the backup stanza when running as primary. Addresses issues #83 and #93 1: pgbackrest/pgbackrest#878
feikesteenbergen
added a commit
that referenced
this issue
Jan 17, 2020
The check command of pgBackRest used to succeed on the replica, but this behaviour changed recently [1] and will be ok in the long term. This commit is a workaround for this change, and will only check the backup stanza when running as primary. Addresses issues #83 and #93 1: pgbackrest/pgbackrest#878
feikesteenbergen
added a commit
that referenced
this issue
Jan 21, 2020
The check command of pgBackRest used to succeed on the replica, but this behaviour changed recently [1] and will be ok in the long term. This commit is a workaround for this change, and will only check the backup stanza when running as primary. Addresses issues #83 and #93 1: pgbackrest/pgbackrest#878
@lonelyleaf We fixed this in the latest release (1.5.1), could you verify that it is solved for you now? |
It is still not solved (
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When using backup featuer in helm chart,only the master pod's
pgbackrest
container canstart up , the log of slave container is like below:
I checked the issues of pgbackrest pgbackrest/pgbackrest#878, so by default only the master db can be backup.
But in a statefuleset ,when
pgbackrest
fail to start the servicetimescaledb-single-replica
won't have available endpoints,causing conneting to slave is imposiableThe text was updated successfully, but these errors were encountered: