Skip to content

[Brook] Removed the reader idle timeout. - #26

Closed
moetemp wants to merge 1 commit into
moe/brook/v3/s9-store-capabilitiesfrom
moe/brook/v4/s10-reads-without-idle
Closed

moetemp wants to merge 1 commit into
moe/brook/v3/s9-store-capabilitiesfrom
moe/brook/v4/s10-reads-without-idle

Conversation

@moetemp

@moetemp moetemp commented Oct 22, 2026

Copy link
Copy Markdown
Owner

What changed?

This PR removes the reader idle timeout from the Stream service.
ReadRecordsRequest.idle_timeout (9) and STREAM_RECORD_KIND_IDLE (4) are now reserved in stream_service.proto, by number and by name. read_records no longer computes an idle deadline or makes an Idle Record. A read ends with the Records it found, the close Record, or an empty page after wait. The test of the Idle Record now checks that a quiet read ends empty after its wait, with next_offset at the place to resume from.

Why?

Decisions S45 and S75. A Reader that wants to stop after a quiet period sets its own timer and resumes from next_offset. A later opt-in idle notification can be added without a break.

How did you test it?

cargo fmt --all -- --check, cargo clippy --workspace --tests -- -D warnings, and STREAMS_REQUIRE=redis cargo test --workspace on standalone Redis, a 3-primary Redis cluster and the memory Store.

@moetemp

moetemp commented Oct 25, 2026

Copy link
Copy Markdown
Owner Author

Closing as stale. This layer is folded into the v5 tip, #41, and the upstream review uses a fresh series instead. Plan: https://www.notion.so/4048fc567738814990b7c796ac28fe3f

@moetemp moetemp closed this Oct 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant