[
https://issues.apache.org/jira/browse/KAFKA-3076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15115061#comment-15115061
]
ASF GitHub Bot commented on KAFKA-3076:
---------------------------------------
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 <[email protected]>
Date: 2016-01-09T10:14:33Z
BrokerChangeListener logging the brokers in order
commit f220ab0de7f09be219e9ddeca3dfb2b8133f390a
Author: Konrad <[email protected]>
Date: 2016-01-11T18:28:35Z
BrokerChangeListener logging refactor
commit 0e73989422611329739fcceeb3925f86374ed925
Author: konradkalita <[email protected]>
Date: 2016-01-12T12:41:35Z
BrokerChangeListener now passes sorted seq to handlers
commit 5005acb629cd934fbaacffb8b371b261dd7d8dc2
Author: Konrad <[email protected]>
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 <[email protected]>
Date: 2016-01-12T16:52:24Z
Merge conflicts resolved
----
> BrokerChangeListener should log the brokers in order
> ----------------------------------------------------
>
> Key: KAFKA-3076
> URL: https://issues.apache.org/jira/browse/KAFKA-3076
> Project: Kafka
> Issue Type: Improvement
> Components: core
> Affects Versions: 0.9.0.0
> Reporter: Jun Rao
> Assignee: Konrad Kalita
> Labels: newbie
>
> Currently, in BrokerChangeListener, we log the full, new and deleted broker
> set in random order. It would be better if we log them in sorted order.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
