[
https://issues.apache.org/jira/browse/KAFKA-3037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15133657#comment-15133657
]
ASF GitHub Bot commented on KAFKA-3037:
---------------------------------------
GitHub user granthenke opened a pull request:
https://github.com/apache/kafka/pull/875
KAFKA-3037: Test number of alive brokers known after single node clus…
…ter startup
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/granthenke/kafka self-aware
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/875.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 #875
----
commit 21ec8efa3a1d218e1bd578a5498d25c8e3d95ee8
Author: Grant Henke <[email protected]>
Date: 2016-02-05T04:52:27Z
KAFKA-3037: Test number of alive brokers known after single node cluster
startup
----
> Number of alive brokers not known after single node cluster startup
> -------------------------------------------------------------------
>
> Key: KAFKA-3037
> URL: https://issues.apache.org/jira/browse/KAFKA-3037
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 0.8.2.1
> Reporter: Stevo Slavic
> Assignee: Grant Henke
> Priority: Minor
>
> Single broker cluster is not aware of itself being alive. This can cause
> failure in logic which relies on number of alive brokers being known - e.g.
> consumer offsets topic creation logic success depends on number of alive
> brokers being known.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
