Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: scalable push query bandwidth throttling #8087

Merged
merged 9 commits into from
Sep 8, 2021

Conversation

nateab
Copy link
Member

@nateab nateab commented Aug 31, 2021

Description

For scalable push queries, once the bandwidth limit is exceeded, do not allow new queries to be created.
Limits the amount of bandwidth used by push queries by using a Sliding Window Log, similar to pull queries. The limit (in MB per hour) can be set using the ksql.query.push.scalable.max.hourly.bandwidth config. Once the limit is hit, scalable push queries will fail immediately.

Testing done

Integration testing added.

Reviewer checklist

  • Ensure docs are updated if necessary. (eg. if a user visible feature is being added or changed).
  • Ensure relevant issues are linked (description should include text like "Fixes #")

@ghost
Copy link

ghost commented Aug 31, 2021

@confluentinc It looks like @nateab just signed our Contributor License Agreement. 👍

Always at your service,

clabot

Copy link
Member

@AlanConfluent AlanConfluent left a comment

Choose a reason for hiding this comment

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

Looking good. Just a couple small comments.

@nateab nateab marked this pull request as ready for review September 8, 2021 00:19
@nateab nateab requested a review from a team as a code owner September 8, 2021 00:19
@nateab nateab merged commit d5af6a1 into confluentinc:master Sep 8, 2021
@nateab nateab deleted the spq_throttling branch September 13, 2021 20:30
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.

2 participants