GitHub user rowdyrabbit opened a pull request:
https://github.com/apache/kafka/pull/822
KAFKA-3103 fix - also fixes KAFKA-3155 and KAFKA-2836
All three defects have the same root cause.
Root cause is ClientUtils.fetchTopicMetadata returns the BrokerEndPoints in
a non-deterministic order, so we need to sort the expected endpoints and the
received endpoints so we can correctly compare them.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/rowdyrabbit/kafka KAFKA-3103
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/822.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #822
----
commit e4322430b5fb5c144d5f7e176250b035bf18bd90
Author: Denise Fernandez <[email protected]>
Date: 2016-01-28T07:23:56Z
KAFKA-3103 fix - also fixes KAFKA-3155 and KAFKA-2836 as they have the same
root cause. Root cause is ClientUtils.fetchTopicMetadata returns the
BrokerEndPoints in a non-deterministic order, so we need to sort the expected
endpoints and the received endpoints so we can correctly compare them.
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
