Skip to content

server-zd v0.1.21

Choose a tag to compare

@longquanzheng longquanzheng released this 07 Nov 07:41
86e1b44

Breaking Changes

  • Upgrade the standby and the active together. Several changes in this release change apply results (#1339, #1358, #1356, #1363, #1368). Stop the standby and the active, upgrade both, then start them. Do not upgrade the standby first: a mixed-version pair can diverge.
  • The history window counts events (#1358). history.windowSemanticEvents is renamed to history.windowEvents and now counts history events instead of semantic commands; history.pruneChunkSize also counts events. The old key still works and logs a deprecation warning at startup; setting both names is an error. Runs started before this version keep their recorded window size, which is now read as an event count, so their window reaches slightly less far back.
  • A GetHistoryEvents page is bounded by the gRPC response limit (#1343). A page ends early when the next event would exceed the response size limit, and the next page token continues from there. Large values in history events are returned as value references; load them with LoadBlobs.

server-zd v0.1.21

Features

  • Only active state counts toward limits.maxFlowStateBytes (#1339). History and the superseded values that history keeps for time travel no longer count, so a long session that rewrites large values no longer fails on its run budget. history.maxRetainedSupersededBytes (256 MiB) now only shortens the time travel range.
  • Per-run history window (#1358). The new public FlowConfig.history_window_events sets how many history events one run keeps. Set it at StartFlow, with UpdateFlowConfig, or in a SubFlow override; children inherit it. Values must be between 1 and history.maxWindowEvents (default 100000).
  • Single-node disk use (#1353). dev and local now default snapshot.logDeletionDelay to 1 hour instead of 24 hours, so the embedded object store stops growing for a full day. serve keeps 24 hours. An explicit value still wins. The configuration reference has a new "Disk use" section.
  • Checkpoint thresholds (#1340). history.checkpointCommandInterval is renamed to history.checkpointCommandThreshold, now defaulting to 1000 commands (was 10000), and history.checkpointMinWrittenBytes to history.checkpointRowWriteBytesThreshold. The old keys still work with a deprecation warning. Flows that rewrite a large value on every Step can lower the command threshold to bound local history.
  • Experimental history offload (off by default; #1341, #1356, #1363, #1368). A partition-scoped mode seals run history into segments, uploads them to the primary object store under history/, and migrates the history of existing runs. It is off by default in every mode. Do not turn it on in this release: reading uploaded history arrives in a later release, so history that was uploaded and pruned locally cannot be read yet.

Fixes

  • Step and history event waits no longer read History rows (#1342).
  • History pages respect the gRPC message limit, and stored effect values are referenced instead of inlined in history events (#1343). Fixes #1338.
  • Task queue tests no longer race with asynchronous Claim replies (#1351).