Survive Contabo PUT throttling in the lake extractor #22

Merged
admin_emi merged 1 commit from fix/lake-put-throttle into dev 2026-07-23 22:47:27 +00:00
Owner

429s at 16 concurrent PUTs killed the run at tile 54/390; adaptive boto3 retries + pool of 8 + per-tile failure isolation. Relaunched run is resuming from the manifest.

429s at 16 concurrent PUTs killed the run at tile 54/390; adaptive boto3 retries + pool of 8 + per-tile failure isolation. Relaunched run is resuming from the manifest.
admin_emi added 1 commit 2026-07-23 22:45:37 +00:00
Survive Contabo PUT throttling in the lake extractor
All checks were successful
PR build (required check) / build-frontend (pull_request) Has been skipped
PR build (required check) / gate (pull_request) Successful in 3s
PR build (required check) / validate-observability (pull_request) Has been skipped
secrets-guard / encrypted (pull_request) Successful in 6s
PR build (required check) / changes (pull_request) Successful in 8s
PR build (required check) / build-backend (pull_request) Successful in 1m3s
33157766cb
Contabo answers 429 to PUT bursts; at 16 concurrent uploads botocore's
default 4 retries ran out and the run died at tile 54/390. Adaptive retry
mode (client-side rate limiting, 10 attempts), a halved upload pool, and
per-tile failure isolation (a failed tile logs and is retried next run —
it never reached the manifest) keep the run alive through throttling.
admin_emi merged commit a787f79f92 into dev 2026-07-23 22:47:27 +00:00
admin_emi deleted branch fix/lake-put-throttle 2026-07-23 22:47:28 +00:00
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Jinemi/thermograph#22
No description provided.