You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Armin Braun (JIRA)" <ji...@apache.org> on 2017/02/15 07:56:41 UTC
[jira] [Created] (KAFKA-4765)
org.apache.kafka.clients.producer.KafkaProducerTest#testConstructorFailureCloseResource
and Similar Tests are Failing on some Systems (127.0.53.53 Collision
Warning)
Armin Braun created KAFKA-4765:
----------------------------------
Summary: org.apache.kafka.clients.producer.KafkaProducerTest#testConstructorFailureCloseResource and Similar Tests are Failing on some Systems (127.0.53.53 Collision Warning)
Key: KAFKA-4765
URL: https://issues.apache.org/jira/browse/KAFKA-4765
Project: Kafka
Issue Type: Bug
Components: unit tests
Affects Versions: 0.10.1.1
Environment: All DNS environments that properly forward 127.0.53.53
Reporter: Armin Braun
Priority: Critical
The test
{code}
org.apache.kafka.clients.producer.KafkaProducerTest#testConstructorFailureCloseResource
{code}
fails on some systems because this below snippet from
{code}
org.apache.kafka.clients.ClientUtils#parseAndValidateAddresses
{code}
{code}
InetSocketAddress address = new InetSocketAddress(host, port);
if (address.isUnresolved()) {
log.warn("Removing server {} from {} as DNS resolution failed for {}", url, CommonClientConfigs.BOOTSTRAP_SERVERS_CONFIG, host);
} else {
addresses.add(address);
}
{code}
will add the address *some.invalid.hostname.foo.bar* to the addresses list without error since it is resolved to *127.0.53.53* to indicate potential future collision of the _.bar_ tld.
The same issue applies to a few other test cases that try to intentionally run into broken hostnames.
This can (and should) be fixed by using broken hostname examples that do not collide. I would suggest just putting a ".local" suffix on all that are currently affected by this.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)