Skip to content

feat: Add lag/idle plot simulator for cost-based autoscaler#19687

Draft
kfaraz wants to merge 6 commits into
apache:masterfrom
kfaraz:visualize_auto_scaler
Draft

feat: Add lag/idle plot simulator for cost-based autoscaler#19687
kfaraz wants to merge 6 commits into
apache:masterfrom
kfaraz:visualize_auto_scaler

Conversation

@kfaraz

@kfaraz kfaraz commented Jul 15, 2026

Copy link
Copy Markdown
Contributor

Description

Tuning the lag-based auto-scaler can sometimes be a little involved.

This patch aims to allow making the process simpler by simulating the optimal task count chosen by the auto-scaler under different conditions.

Changes currently in this PR

  • UI code is generated by Claude and may contain mistakes
  • Add a simulate API currently supported for Kafka supervisors only
  • This API creates a CostBasedAutoScaler in "simulate" mode and generates the optimal task count for various input values of lag (based on criticalLag)
  • Add a UI panel in the supervisor dialog which shows up only for "kafka" supervisors
  • Add a single plot between task count vs lag

Web-console screenshot

Screenshot 2026-07-15 at 2 31 16 PM

Other required changes

  • Use a POST API instead of GET so that the current autoscalerConfig may be sent as payload
  • Wire up the UI side so that changes made in the simulate window are reflected in the autoscalerConfig and vice versa
  • Fix up the taskIdleRatio field to accept decimal numbers, currently the field resets to integers
  • Maybe more plots that help the user make a more informed decision
  • Perhaps a plot with the task idleness as well

This PR has:

  • been self-reviewed.
  • added documentation for new or modified features or behaviors.
  • a release note entry in the PR description.
  • added Javadocs for most classes and all non-trivial methods. Linked related entities via Javadoc links.
  • added or updated version, license, or notice information in licenses.yaml
  • added comments explaining the "why" and the intent of the code wherever would not be obvious for an unfamiliar reader.
  • added unit tests or modified existing tests to cover new code paths, ensuring the threshold for code coverage is met.
  • added integration tests.
  • been tested in a test Druid cluster.

@kfaraz
kfaraz requested a review from Fly-Style July 15, 2026 08:50
}

@GET
@Path("/{id}/autoscaler")

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We will rename this API based on what we decide the final result set to look like:

Suggested change
@Path("/{id}/autoscaler")
@Path("/{id}/autoscaler/simulate")

Comment on lines +544 to +548
@QueryParam("taskCountMin") int taskCountMin,
@QueryParam("taskCountMax") int taskCountMax,
@QueryParam("maxProcessingRatePerTask") int maxProcessingRatePerTask,
@QueryParam("optimalTaskIdleRatio") double optimalTaskIdleRatio,
@QueryParam("criticalLag") int criticalLag,

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Instead of multiple query params, we should just be able to send a POST payload object as a CostBasedAutoScalerConfig.

@QueryParam("idleWeight") Double idleWeight,
@QueryParam("criticalLag") int criticalLag,
@QueryParam("currentTaskCount") Integer currentTaskCount,
@Context HttpServletRequest request
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants