Skip to content

Conversation

@dpkp
Copy link
Owner

@dpkp dpkp commented May 25, 2018

Fixes #1473 . This change drops the DNS retries that I had originally included. This should return us to the prior behavior where attempting to start a kafka-python client with invalid bootstrap metadata (or a failing DNS system) will raise an exception.

@jeffwidman
Copy link
Contributor

jeffwidman commented May 25, 2018

See comments in #1473 (comment)

@dpkp dpkp merged commit 39ebe1d into master May 26, 2018
@dpkp dpkp deleted the connect_blocking_fixups branch May 26, 2018 17:52
ofek pushed a commit to DataDog/integrations-core that referenced this pull request May 29, 2018
This bumps to 1.4.3 which removed the DNS retries when the bootstrap
brokers list contained a failing broker:
dpkp/kafka-python#1507
@svvitale
Copy link

Hi @dpkp, thanks for this update. I'm working through integrating it now, but I'm finding that when I instantiate a KafkaProducer with invalid bootstrap information, it does not raise an exception. It returns a valid instance, and I can't tell that anything is wrong until I actually try to send data. From your description, it sounds like this should be happening earlier. Which behavior is correct?

88manpreet pushed a commit to Yelp/kafka-python that referenced this pull request Aug 1, 2018
* only perform single dns lookup for connect_blocking()
* fix blocking timeout in check_version()
88manpreet pushed a commit to Yelp/kafka-python that referenced this pull request Aug 1, 2018
* only perform single dns lookup for connect_blocking()
* fix blocking timeout in check_version()
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants