Skip to content

Bump auto-enroll autoscaling minimum to the fixed poller default - #2977

Draft
veeral-patel wants to merge 1 commit into
mainfrom
veeral/poller-autoenroll-explicit-defaults
Draft

Bump auto-enroll autoscaling minimum to the fixed poller default#2977
veeral-patel wants to merge 1 commit into
mainfrom
veeral/poller-autoenroll-explicit-defaults

Conversation

@veeral-patel

@veeral-patel veeral-patel commented Jul 29, 2026

Copy link
Copy Markdown
Contributor

Why

When a worker auto-enrolls into poller autoscaling (via the PollerAutoscalingAutoEnroll namespace capability), it previously started with a minimum of 1 poller. That's fewer than the fixed default (5) a worker would otherwise run, so auto-enrolling could cause a throughput regression from too few pollers.

This sets the autoscaling minimum equal to the fixed default poller count, so auto-enrolling never starts below what a non-autoscaling worker would use.

What

Auto-enroll now uses explicit values:

min max initial
5 (fixed default) 100 5

Applies to workflow, activity, and nexus pollers.

Tested: ./gradlew :temporal-sdk:test --tests "*PollerAutoscalingAutoEnroll*" --tests "*WorkerPollerAutoEnroll*" passes. Updated one assertion to expect PollerBehaviorAutoscaling(5, 100, 5).

When auto-enrolling into poller autoscaling via the PollerAutoscalingAutoEnroll
namespace capability, construct PollerBehaviorAutoscaling with explicit
min/max/initial (5/100/5) instead of the no-arg default constructor.
@veeral-patel veeral-patel changed the title Set explicit min/max/initial for auto-enroll poller autoscaling Bump auto-enroll autoscaling minimum to the fixed poller default Jul 29, 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