You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We usually see these "extractOne: Interpret failed: Interpret: copy failed" messages when there's no disk space left and the specified volume is too small for the database cluster that is about to get cloned. To me the logs looks like the operator is working as expected - which is only setting the right environment variables for Spilo so wal-e will be called to pull a backup and apply WAL files.
Wal-e crashed ("wal-e backup-fetch exited with exit code -9"), hence clone is retried. Maybe specify more memory?
Cloning from existing master works, but is greatly limited by the fact that it has to be the exact same namespace. We are only using it right now cause we are in a pinch and really want to get some tests done.
Clone fails when attempting to use s3.
Commented on this issue too: #773
pod logs
Nothing notable in operator logs
operator_logs.txt
The text was updated successfully, but these errors were encountered: