GitHub user konradkalita reopened a pull request:
https://github.com/apache/kafka/pull/749
KAFKA-3076: BrokerChangeListener should log the brokers in order
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/konradkalita/kafka kafka-3076
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/749.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 #749
----
commit acbc58b4fed89ff36bbf530c1cf4c3e8f8dd7469
Author: Konrad <konkal...@gmail.com>
Date: 2016-01-09T10:14:33Z
BrokerChangeListener logging the brokers in order
commit f220ab0de7f09be219e9ddeca3dfb2b8133f390a
Author: Konrad <konkal...@gmail.com>
Date: 2016-01-11T18:28:35Z
BrokerChangeListener logging refactor
commit 0e73989422611329739fcceeb3925f86374ed925
Author: konradkalita <konkal...@gmail.com>
Date: 2016-01-12T12:41:35Z
BrokerChangeListener now passes sorted seq to handlers
commit 5005acb629cd934fbaacffb8b371b261dd7d8dc2
Author: Konrad <konkal...@gmail.com>
Date: 2016-01-12T16:34:19Z
Merge branch 'trunk' into kafka-3076
# Conflicts:
# core/src/main/scala/kafka/controller/ReplicaStateMachine.scala
commit 2d81ab6ea67b5ec1571619851f76b480c7e6a312
Author: Konrad <konkal...@gmail.com>
Date: 2016-01-12T16:52:24Z
Merge conflicts resolved
----
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
