kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-3096) Leader is not set to -1 when it is shutdown if followers are down
Date Mon, 15 May 2017 23:10:04 GMT

    [ https://issues.apache.org/jira/browse/KAFKA-3096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16011478#comment-16011478
] 

ASF GitHub Bot commented on KAFKA-3096:
---------------------------------------

Github user asfgit closed the pull request at:

    https://github.com/apache/kafka/pull/3031


> Leader is not set to -1 when it is shutdown if followers are down
> -----------------------------------------------------------------
>
>                 Key: KAFKA-3096
>                 URL: https://issues.apache.org/jira/browse/KAFKA-3096
>             Project: Kafka
>          Issue Type: Bug
>    Affects Versions: 0.9.0.0
>            Reporter: Ismael Juma
>            Assignee: Ismael Juma
>              Labels: reliability
>
> Assuming a cluster with 2 brokers with unclear leader election disabled:
> 1. Start brokers 0 and 1
> 2. Perform partition assignment
> 3. Broker 0 is elected leader
> 4. Produce message and wait until metadata is propagated
> 6. Shutdown follower
> 7. Produce message
> 8. Shutdown leader
> 9. Start follower
> 10. Wait for leader election
> Expected: leader is -1
> Actual: leader is 0
> We have a test for this, but a bug in `waitUntilLeaderIsElectedOrChanged` means that
`newLeaderOpt` is not being checked.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message