You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
In a scenario where all kafka brokers have been shut down, an application may also want to shut down (or at least stop consumers). Consumer.stop() can get blocked, cycling endlessly to confirm the group coordinator id:
Describe the bug
In a scenario where all kafka brokers have been shut down, an application may also want to shut down (or at least stop consumers). Consumer.stop() can get blocked, cycling endlessly to confirm the group coordinator id:
https://github.com/aio-libs/aiokafka/blob/v0.6.0/aiokafka/consumer/group_coordinator.py#L535-L541
the NodeNotReadyError received in this case is marked as retriable, so the loop continues.
Expected behaviour
Consumer.stop() should be able to complete
Environment (please complete the following information):
python -c "import aiokafka; print(aiokafka.__version__)"
): 0.6.0python -c "import kafka; print(kafka.__version__)"
): 2.0.1kafka-topics.sh --version
): 2.3.0Reproducible example
# Add a short Python script or Docker configuration that can reproduce the issue.
The text was updated successfully, but these errors were encountered: