clickhouse-backup server consumes memory when idle after first backup #841
Replies: 5 comments 18 replies
-
which clickhouse-backup version do you use? |
Beta Was this translation helpful? Give feedback.
-
most of allocations required during UPLOAD/DOWNLOAD inside remote storage related SDKs |
Beta Was this translation helpful? Give feedback.
-
what mean |
Beta Was this translation helpful? Give feedback.
-
could you also run and share |
Beta Was this translation helpful? Give feedback.
-
Hello everyone, we currently have the scenario that our memory utilization often shoots up when creating a backup. However, this only happens when uploading the last table (approx. 10 GB), after which the memory utilization remains this high. Setup details:
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Why clickhouse-backup server container placed as a sidecar inside clickhouse server pod consumes memory when idle after first backup succeed. Using remote backups on gcs. When just started, container consumes tens of Mi. But after backup made and uploaded, it consumes couple Gi of memory whole day being idle.
Image:
altinity/clickhouse-backup:2.4.30
Default config overrides:
Other gcs and clickhouse creds related config set over env variables.
Any ideas how to deal with such issue? Whole pod restart after each backup not an option.
Beta Was this translation helpful? Give feedback.
All reactions