-
Notifications
You must be signed in to change notification settings - Fork 310
Open
Labels
bugSomething isn't workingSomething isn't working
Description
Bug Description
Chunk size of 5242880 exceeds 1 MiB maximum.
Environment
Litestream version:
v0.5.0-test.2
Operating system & version:
Installation method:
Docker litestream/litestream:0.5.0-test.2
Storage backend:
S3 Backblaze B2
Steps to Reproduce
- Step one
- Step two
- Step three
Expected behavior:
Actual behavior:
Configuration
litestream.yml
dbs:
- path: /data/data.sqlite
replicas:
- type: s3
bucket: bucket
path: prod
endpoint: https://s3.eu-central-003.backblazeb2.com
region: eu-central-003
force-path-style: true
part-size: 1MB
concurrency: 10
sync-interval: 30s
access-key-id: "-"
secret-access-key: "-"
Logs
Log output
time=2025-09-14T23:29:38.546Z level=INFO msg=litestream version=v0.5.0-test.2 level=""
time=2025-09-14T23:29:38.547Z level=INFO msg="initialized db" path=/data/data.sqlite
time=2025-09-14T23:29:38.547Z level=INFO msg="replicating to" type=s3 sync-interval=30s bucket=bucket path=prod region=eu-central-003 endpoint=https://s3.eu-central-003.backblazeb2.com
time=2025-09-14T23:29:38.547Z level=INFO msg="starting compaction monitor" level=1 interval=5m0s
time=2025-09-14T23:29:38.547Z level=INFO msg="starting compaction monitor" level=9 interval=24h0m0s
time=2025-09-14T23:29:38.547Z level=INFO msg="starting compaction monitor" level=2 interval=1h0m0s
time=2025-09-14T23:29:41.425Z level=ERROR msg="compaction failed" level=9 error="s3: upload to prod/0009/0000000000000001-0000000000000001.ltx: upload multipart failed, upload id: 4_z169cefd3ae4809039f51021c_f239fafc2d9820704_d20250914_m232941_c003_v0312029_t0040_u01757892581189, cause: operation error S3: UploadPart, https response error StatusCode: 400, RequestID: b5daa1287affd177, HostID: aNiNj5WZAMwdlpTi0OQwzI2aIMT4yB2Op, api error InvalidArgument: Chunk size of 5242880 exceeds 1 MiB maximum."
Additional Context
Add any other context about the problem here (e.g., recent changes, related issues, workarounds you've tried).
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working