-
Notifications
You must be signed in to change notification settings - Fork 854
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
Consumer Hangs while Dispose in K8s #2013
Comments
Some issues we encountered as well in K8S. |
@paul-cheung This message/situation is unrelated to this issue (though to be fair, this issue is of the "stuff is going wrong sometimes in our environment; we have not narrowed it down" variety which is hard for the maintainers to produce). The config value the message cites is the maximum amount of time your code is allowed between polling for a message from the client. In other words, it's saying "you said I was to assume you're dead if you took more than 5 minutes to come back and ask for the next message. This is your notice that you took 151ms longer and we automatically removed you from the healthy clients list in accordance with that". Your choices are to either guarantee to check more frequently by adjusting your code, or extend that poll interval. |
@ksdvishnukumar I do not get which one is true :P
is it In my case I'm calling |
@plachor, I encountered this issue some times close to 10 min and some time even 1 hr (Pipeline Max Timeout). Since am using Azure Pipeline to deploy the pod in AKS, Pipeline has 1hr Max Time out. After that it times out. I also use the same way as you mentioned try |
Description
I have a case where the consumer hangs indefinitely almost 10 Minutes, and I cannot figure out why.
I use Confluent Kafka to connect to Eventhub.
I have 3 instances of application running. Out of that 2 are getting disposed faster. But 1 hangs. This scenario is not happening all the time but 20% (1/5) its happening.
How to reproduce
Its a very simple Consumer application you can use.
Checklist
Please provide the following information:
The text was updated successfully, but these errors were encountered: