[kafka_consumer] Kafka client takes 2 minutes to time out #1589
Milestone
Comments
LeoCavaille
added a commit
that referenced
this issue
May 4, 2015
Because the default timeouts are pretty high in the kafka-python and kazoo library (resp. 120s and 10s), we put them at a much lower threshold (5s) for the default cases and offer a way to override in the YAML init_config section. Fixes #1589.
LeoCavaille
added a commit
that referenced
this issue
May 6, 2015
Because the default timeouts are pretty high in the kafka-python and kazoo library (resp. 120s and 10s), we put them at a much lower threshold (5s) for the default cases and offer a way to override in the YAML init_config section. Fixes #1589.
LeoCavaille
added a commit
that referenced
this issue
May 6, 2015
Because the default timeouts are pretty high in the kafka-python and kazoo library (resp. 120s and 10s), we put them at a much lower threshold (5s) for the default cases and offer a way to override in the YAML init_config section. Fixes #1589.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If the KafkaClient can not connect to kafka, it takes 2 minutes to time out. The code at https://github.com/DataDog/dd-agent/blob/5.2.x/checks.d/kafka_consumer.py#L59-L72 is using the default timeout for kafka-client, which is 120 seconds: https://github.com/mumrah/kafka-python/blob/92aa7e94288cbfc4aed0dfbd52021d21694bced4/kafka/conn.py#L14
During the time that it's trying to connect to kafka, no data is reported by the agent.
The text was updated successfully, but these errors were encountered: