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

Decouple stream halt detection timeout from max poll interval #1376

Merged
merged 14 commits into from
Nov 13, 2024

Conversation

svroonland
Copy link
Collaborator

Fixes #1262

@svroonland svroonland marked this pull request as ready for review November 10, 2024 20:09
svroonland and others added 3 commits November 10, 2024 21:09
Also:
 - restore some scaladoc
 - simpler way to get `maxPollInterval`
 - more warnings for providing java consumer
* Make sure that all records from a single poll (see [[withMaxPollRecords maxPollRecords]]) can be processed in this
* interval, even when there is no concurrency because the records are all in the same partition.
*
* The default is equal to [[withMaxPollInterval maxPollInterval]]).
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Is this still correct, if so where is it set?

Copy link
Collaborator

Choose a reason for hiding this comment

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

In RunloopAccess:

maxStreamPullInterval = settings.maxStreamPullIntervalOption.getOrElse(maxPollInterval)

@svroonland svroonland merged commit 504074f into master Nov 13, 2024
14 checks passed
@svroonland svroonland deleted the stream-halt-detection-timeout branch November 13, 2024 10:04
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.

Runaway stream when max.poll.interval.ms is exceeded
2 participants