* seaweed-volume: bound each FetchAndWriteNeedle replica write
A replica that accepted the connection and then went silent held the
request until TCP gave up, because the shared outgoing client has no
request timeout. Each replica write now fails after 30 s, from connect
to the response status, matching the Go volume server.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* volume: bound each FetchAndWriteNeedle replica write
The default replica path uploads through the guarded peer client, which
bounds only the dial and has no response header timeout, and the filer
calls FetchAndWriteNeedle with no deadline. A replica that accepted the
connection and went silent held the request for minutes. Each replica
write, retries included, now has 30 s.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* seaweed-volume: require the silent-peer test to fail at the deadline
A connection error that came back early also passed, since the test
only checked an upper bound. It now also requires the paused clock to
have reached FETCH_AND_WRITE_REPLICA_TIMEOUT.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* seaweed-volume: grow the FetchAndWriteNeedle replica bound with the chunk
The reqwest timeout includes sending the body, and a remote-cache chunk
is a thousandth of the object once it passes the 1000-chunk cap, so a
fixed 30 s would fail a large chunk on a link under ~35 MB/s. The bound
is now 30 s plus 1 s per MiB.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* volume: grow the FetchAndWriteNeedle replica bound with the chunk
The context deadline includes sending the body, so a fixed 30 s would
fail a large remote-cache chunk on a slow link. The bound is now 30 s
plus 1 s per MiB, matching the Rust volume server.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
