-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Unexpected user-specified time limit error still occurs #1758
Comments
I am experiencing the the same problem. |
@qiuxuxu1 To me, It seems no problem while consuming the data (looks like this request will be retried). |
I have the same problem with sarama v1.17.2. |
I am having same issue.. error logs are printing. in my case I set auto commit to false |
Experiencing the same with Sarama v1.29.1 (current latest).
|
This comment was marked as outdated.
This comment was marked as outdated.
We need to resurrect #2040 and see if that solves the OP's issues |
@dnwe
Is it safe to ignore this error? And does this timeout error have no effect on consume result due to request retry? |
@mingdyuo for that error you should either increase your sarama/examples/consumergroup/main.go Lines 180 to 204 in 9b0419d
|
I modified it not to block processing like the example code, but same error still occurs time sometimes. |
Thank you for taking the time to raise this issue. However, it has not had any activity on it in the past 90 days and will be closed in 30 days if no updates occur. |
ping? |
Versions
Please specify real version numbers or git SHAs, not just "Latest" since that changes fairly regularly.
Configuration
What configuration values are you using for Sarama and Kafka?
Logs
When filing an issue please provide logs from Sarama and Kafka if at all
possible. You can set
sarama.Logger
to alog.Logger
to capture Sarama debugoutput.
logs: CLICK ME
Problem Description
This was the original issue (#1562)
After I update Sarama version to v1.26.4 and cleaned config values but, I still got
unexpected user-specified time limit
errors from the broker while consuming the topic. Is it related to theBroker
issue? or Can we do anything from the client-side?Below is the code where the error comes from.
The text was updated successfully, but these errors were encountered: