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
In the Kafka-python documentation, it states that if at least one host of the connection is up and able to respond to the Metadata API Request, the connection should be fine.
However, connection is failing silently; I only noticed because messages were not being consumed.
Kafka-python 2.0.2, consumer is running on a docker image hosted in an AWS EC2.
My configuration is straightforward: consumer = KafkaConsumer( 'mytopic', group_id=group_id, bootstrap_servers=['host1:port1','host2:port2','host3:port3','host4:port4'], security_protocol='SSL' )
This works when all hosts are healthy but fails if there is a typo on the hostname or a host is unhealthy.
For this bug, I would expect that connection to succeed despite one host not being accessible as long at least of the list it is. And in the worst case scenario a failure to connect.
The text was updated successfully, but these errors were encountered:
I think I found an issue connecting to MSK.
In the Kafka-python documentation, it states that if at least one host of the connection is up and able to respond to the Metadata API Request, the connection should be fine.
However, connection is failing silently; I only noticed because messages were not being consumed.
Does that relate to dpkp#2390 and dpkp#2281?
Kafka-python 2.0.2, consumer is running on a docker image hosted in an AWS EC2.
My configuration is straightforward:
consumer = KafkaConsumer( 'mytopic', group_id=group_id, bootstrap_servers=['host1:port1','host2:port2','host3:port3','host4:port4'], security_protocol='SSL' )
This works when all hosts are healthy but fails if there is a typo on the hostname or a host is unhealthy.
For this bug, I would expect that connection to succeed despite one host not being accessible as long at least of the list it is. And in the worst case scenario a failure to connect.
The text was updated successfully, but these errors were encountered: