Skip to content

feat(precompute): separate idle and deadline closure - #486

Merged
zzylol merged 1 commit into
mainfrom
feat/precompute-window-close-policy
Sep 3, 2026
Merged

zzylol merged 1 commit into
mainfrom
feat/precompute-window-close-policy

Conversation

@zzylol

@zzylol zzylol commented Sep 3, 2026

Copy link
Copy Markdown
Contributor

Before

The precompute worker used a single wall-clock grace concept, so an idle timeout and an absolute maximum-open deadline could not be configured or reasoned about independently.

After

  • Track pane first-touch and last-touch wall-clock timestamps separately.
  • Add distinct wall_clock_idle_grace_period_ms and wall_clock_max_open_grace_period_ms settings.
  • Keep the old wall_clock_grace_period_ms spelling as a deserialize-only alias for idle grace.
  • Close idle panes using last activity and bound continuously active panes using the absolute deadline.
  • Add regressions for active ingestion and deadline closure.

Validation

  • cargo fmt -p data_plane -- --check
  • CARGO_TARGET_DIR=/mydata/ASAPQuery-backend/target cargo test -p data_plane precompute_engine:: (262 passed at this stack stage)

Supersedes #484, which GitHub automatically closed when its merged base branch was deleted.

@zzylol
zzylol merged commit 343e53f into main Sep 3, 2026
2 checks passed
@zzylol
zzylol deleted the feat/precompute-window-close-policy branch September 12, 2026 14:48
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