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
{{ message }}
This repository has been archived by the owner on Mar 28, 2020. It is now read-only.
I think what's happening is the operation is getting canceled because the snapshot timeout (60s) is too short. This cluster is creating etcd snapshots of about 260mb. I have another cluster with snapshots around 50mb that are able to save successfully.
Is the snapshot timeout something we could consider increasing, or make configurable? Thanks
The text was updated successfully, but these errors were encountered:
It looks like it may have been CPU bound. My default resource request/limit was 50m/50m. I increased the operator to 250m/250m and it finished successfully. I think my metrics aren't granular enough to show the CPU starvation.
I did time the snapshot save:
etcd-0 ~ $ ETCDCTL_API=3 time etcdctl --endpoints="https://127.0.0.1:2379" --cacert="/etc/ssl/etcd/ca.crt" snapshot save test.db
Snapshot saved at test.db
real 0m5.926s
user 0m1.168s
sys 0m0.499s
In any case, I think this issue is still valid, the timeout probably should be configurable. Also if the docs mentioned minimum recommended resource requirements that might save someone some trouble. Thanks!
I have a cluster that is failing to backup to S3 with the following logs:
I think what's happening is the operation is getting canceled because the snapshot timeout (60s) is too short. This cluster is creating etcd snapshots of about 260mb. I have another cluster with snapshots around 50mb that are able to save successfully.
Is the snapshot timeout something we could consider increasing, or make configurable? Thanks
The text was updated successfully, but these errors were encountered: