-
-
Notifications
You must be signed in to change notification settings - Fork 157
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
Can not flush when MaxBufferedRecords reached #726
Labels
Comments
twmb
added a commit
that referenced
this issue
May 23, 2024
Currently if your linger is long and your max records small, it is possible to linger even if the client cannot buffer any more records. Now, once max records or bytes is hit, we wakeup anything lingering and avoid entering the linger state again -- until we are no longer over max. Closes #726.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
#591
According this, I think when records will be flushed when linger is hit or batch is full.
But it always flush per 10s, when I reach buffer size, it will just block and do not flush.
The text was updated successfully, but these errors were encountered: