Konstantin Adzer 42b0ca7850 s3 sink: report the source read error the SDK hides (#11277) ...

* s3 sink: report the source read error the SDK hides

filer.backup stops for good on an event whose chunks are gone from the
volume servers: the uploader reads the body, the read fails with the
volume's 404, and the AWS SDK returns "ContentLength=N with Body length 0"
without the cause. isIgnorable404 would skip such an event, but it never
sees the 404, so the event is retried forever and the checkpoint never
advances.

ChunkStreamReader keeps its first source failure and the s3 sink returns
it when the upload fails.

* s3 sink: trim verbose comments on source error propagation

---------

Co-authored-by: Chris Lu <chris.lu@gmail.com>

2026-09-11 19:44:30 -07:00

..

repl_util

filer: authorize the chunk proxy and the root listing like the rest of the filer port (#11152)

2026-09-04 16:39:36 -07:00

sink

s3 sink: report the source read error the SDK hides (#11277)

2026-09-11 19:44:30 -07:00

source

filer: authorize the chunk proxy and the root listing like the rest of the filer port (#11152)

2026-09-04 16:39:36 -07:00

sub

filer.replicate: acknowledge notifications after the sink write, not on receipt (#10427)

2026-07-24 10:43:48 -07:00

replicator_test.go

filer.backup, filer.sync: stop sharing resume checkpoints across destinations (#10934)

2026-08-24 19:30:20 -07:00

replicator.go

fix(filer.sync): replicate a rename as an atomic move, not a no-op update (#9895)

2026-06-09 12:54:28 -07:00