WIP: Add scale_decisions to WorkerPollerInfo#823
Open
veeral-patel wants to merge 1 commit into
Open
Conversation
veeral-patel
changed the title
veeral-patel
added a commit
to temporalio/sdk-go
that referenced
this pull request
Jul 9, 2026
The poller autoscaler now counts its scale decisions internally (keyed by reason: server_up, server_up_suppressed, server_down, empty_poll_down, re_halve, error_down, clamp_min, clamp_max). Each worker heartbeat reports the per-interval breakdown per poller type via the new WorkerPollerInfo.scale_decisions field, so scaling behavior — including server-requested scale-ups suppressed by the throughput gate — is observable server-side without a metrics pipeline. Requires the scale_decisions field from temporalio/api#823.
veeral-patel
added a commit
to temporalio/sdk-go
that referenced
this pull request
Jul 9, 2026
The poller autoscaler now counts its scale decisions internally (keyed by reason: server_up, server_up_suppressed, server_down, empty_poll_down, re_halve, error_down, clamp_min, clamp_max). Each worker heartbeat reports the per-interval breakdown per poller type via the new WorkerPollerInfo.scale_decisions field, so scaling behavior — including server-requested scale-ups suppressed by the throughput gate — is observable server-side without a metrics pipeline. Requires the scale_decisions field from temporalio/api#823.
veeral-patel
added a commit
to temporalio/sdk-go
that referenced
this pull request
Jul 9, 2026
The poller autoscaler now counts its scale decisions, keyed by reason (server_up, server_up_suppressed, server_down, empty_poll_down, re_halve, error_down). Each worker heartbeat reports the per-interval breakdown per poller type via the new WorkerPollerInfo.scale_decisions field, so scaling behavior — including server-requested scale-ups suppressed by the throughput gate — is observable server-side without a metrics pipeline. Requires the scale_decisions field from temporalio/api#823.
Adds a per-poller-type breakdown of poller autoscaler scale decisions since the last heartbeat (keyed by reason, e.g. server_up, server_up_suppressed, empty_poll_down, re_halve) to the worker heartbeat, so scaling behavior is observable server-side without a metrics pipeline.
veeral-patel
force-pushed
the
veeral/poller-scale-decisions
branch
from
a8a27ca to
70de22e
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Adds a
map<string, int64> scale_decisionsfield (tag 4) toWorkerPollerInfo.It carries a per-poller-type breakdown of poller autoscaler scale decisions since the last heartbeat, keyed by reason:
server_up,server_up_suppressed,server_down,empty_poll_down,re_halve,error_down. Only set when the poller count is auto-scaled.Why
Poller autoscaling decisions (including when a server-requested scale-up is suppressed because the worker's throughput gate is closed) are currently only visible via SDK metrics. Surfacing them in the worker heartbeat makes scaling behavior observable server-side without a metrics pipeline.
Consumer
Go SDK: temporalio/sdk-go (companion PR wires up the SDK to populate this field per interval).