Latest Results
fix(io): enforce read timeouts on OpenDAL clients
OpenDAL's default operator stack carries no deadlines and its shared
HTTP client never times out, so reads through OpenDAL-backed sources
(oss, cos, obs, tos, goosefs, hdfs) hang forever when a connection is
silently dropped, e.g. a load balancer reaping idle connections
without a RST.
Layer OpenDAL's TimeoutLayer (60s per control operation, 10s between
body reads) on the read path of every operator built by
OpenDALSource, overridable per backend via the timeout_ms /
io_timeout_ms config keys (milliseconds, 1..=86400000; malformed or
out-of-range values fail client creation).
Writes and deletes keep their previous unbounded behavior: io_timeout
bounds the whole body of a write call, so any finite default would
also cap how long a part upload may take and break slow-but-legitimate
uploads.
Fixes #7522everySympathy:fix/opendal-timeout fix(io): enforce read timeouts on OpenDAL clients
OpenDAL's default operator stack carries no deadlines and its shared
HTTP client never times out, so reads through OpenDAL-backed sources
(oss, cos, obs, tos, goosefs, hdfs) hang forever when a connection is
silently dropped, e.g. a load balancer reaping idle connections
without a RST.
Layer OpenDAL's TimeoutLayer (60s per control operation, 10s between
body reads) on the read path of every operator built by
OpenDALSource, overridable per backend via the timeout_ms /
io_timeout_ms config keys (milliseconds, 1..=86400000; malformed or
out-of-range values fail client creation).
Writes and deletes keep their previous unbounded behavior: io_timeout
bounds the whole body of a write call, so any finite default would
also cap how long a part upload may take and break slow-but-legitimate
uploads.
Fixes #7522everySympathy:fix/opendal-timeout Latest Branches
0%
everySympathy:fix/opendal-timeout 0%
FANNG1:deprecate-write-lance-merge 0%
slade/deprecate-hf-bearer-token © 2026 CodSpeed Technology