fix(clickhouse): resilient clickhouse-backup fetch (cache/retry/non-blocking) #1

Closed
autonomic-bot wants to merge 1 commits from ci/clickhouse-backup-resilient into main

Hardens entrypoint.clickhouse.sh so a transient GitHub download failure of the clickhouse-backup binary cannot crash-loop the clickhouse-server. Caches on the persistent /var/lib/clickhouse volume, retries with backoff, never blocks server start (clickhouse-backup is the backup tool, not a server dependency), un-silences wget. Enables cc-ci full-lifecycle testing (Q4.7b). No behaviour change when the first download succeeds.

Hardens entrypoint.clickhouse.sh so a transient GitHub download failure of the clickhouse-backup binary cannot crash-loop the clickhouse-server. Caches on the persistent /var/lib/clickhouse volume, retries with backoff, never blocks server start (clickhouse-backup is the backup tool, not a server dependency), un-silences wget. Enables cc-ci full-lifecycle testing (Q4.7b). No behaviour change when the first download succeeds.
autonomic-bot added 1 commit 2026-05-31 05:28:26 +00:00
The published entrypoint downloads the 22MB clickhouse-backup binary from GitHub at container boot
with 'set -ex' + a single silenced no-retry wget to ephemeral /tmp. Any transient failure of that
download (rate-limit / network) exits the container BEFORE clickhouse-server starts, so swarm restarts
it, it re-downloads, and the throttle is amplified into a crash-loop (deploy timeout).

clickhouse-backup is the BACKUP tool (backupbot pre/post hooks), not required for clickhouse-server to
run. This hardening caches the binary on the persistent /var/lib/clickhouse volume (fetched at most
once, reused on restart), retries with backoff, never blocks the server start on a fetch failure, and
un-silences the wget for diagnosability. No behaviour change when the first download succeeds.
Author
Owner

@notplants — flagging this open PR from the cc-ci build for your review. Per the updated mirror workflow we no longer auto-close superseded/unrelated PRs, so it's left open for you to merge or close at your discretion.

@notplants — flagging this open PR from the cc-ci build for your review. Per the updated mirror workflow we no longer auto-close superseded/unrelated PRs, so it's left open for you to merge or close at your discretion.
Author
Owner

!testme

!testme
Author
Owner

🌻 cc-ciplausible @ bd8bd93d failure

cc-ci result card

level

full logs · dashboard

<!-- cc-ci:testme --> 🌻 **cc-ci** — `plausible` @ `bd8bd93d` ❌ **failure** [![cc-ci result card](https://ci.commoninternet.net/runs/122/summary.png)](https://drone.ci.commoninternet.net/recipe-maintainers/cc-ci/122) [![level](https://ci.commoninternet.net/runs/122/badge.svg)](https://drone.ci.commoninternet.net/recipe-maintainers/cc-ci/122) [full logs](https://drone.ci.commoninternet.net/recipe-maintainers/cc-ci/122) · [dashboard](https://ci.commoninternet.net/)
Author
Owner

Superseded by #3 (rebased onto the current entrypoint comments, version corrected to 3.1.0+v2.0.0). Closing.

Superseded by #3 (rebased onto the current entrypoint comments, version corrected to 3.1.0+v2.0.0). Closing.
autonomic-bot closed this pull request 2026-06-09 15:45:08 +00:00
Some checks failed
cc-ci/testme cc-ci: failure

Pull request closed

Sign in to join this conversation.
No Reviewers
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: recipe-maintainers/plausible#1
No description provided.