Skip to content

Apply throttling in response to commit upload backlog - #155652

Draft
lkts wants to merge 1 commit into
elastic:mainfrom
lkts:upload_queue_controller
Draft

Apply throttling in response to commit upload backlog#155652
lkts wants to merge 1 commit into
elastic:mainfrom
lkts:upload_queue_controller

Conversation

@lkts

@lkts lkts commented Jul 31, 2026

Copy link
Copy Markdown
Contributor

No description provided.

/// to the latest data point.
/// We use a slight recency biased value.
/// We also use an optimistic initial value of 1 Gb/sec to run unrestricted on a fresh node.
/// This based on an assumption that a node provides 15 Gigabit max network throughput (which is about ~1.7 GiB).

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.

This is of course not true for small index pods. Alternative we could start with 0 and ensure we ignore decisions based on zero throughput. In this case however we would under count the throughput because of the alpha value.

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 could also not initialize this until we see the first data point with something like SetOnce?

@lkts
lkts force-pushed the upload_queue_controller branch from 2dfc2c2 to 589c7b3 Compare July 31, 2026 21:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants