[
https://issues.apache.org/jira/browse/KAFKA-7209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16558748#comment-16558748
]
Matthias J. Sax commented on KAFKA-7209:
----------------------------------------
Would be good to verify. If broker-only and streams-only fail-over works, it
seems to be a bug if "double fail over" does not work. It's unclear though, if
it's a stream, consumer, or broker bug. Do the broker fail over correctly if
you kill the machine (ie, broker and streams at once)?
> Kafka stream does not rebalance when one node gets down
> -------------------------------------------------------
>
> Key: KAFKA-7209
> URL: https://issues.apache.org/jira/browse/KAFKA-7209
> Project: Kafka
> Issue Type: Bug
> Components: streams
> Affects Versions: 0.11.0.1
> Reporter: Yogesh BG
> Priority: Critical
>
> I use kafka streams 0.11.0.1session timeout 60000, retries to be int.max and
> backoff time default
>
> I have 3 nodes running kafka cluster of 3 broker
> and i am running the 3 kafka stream with same
> [application.id|http://application.id/]
> each node has one broker one kafka stream application
> everything works fine during setup
> i bringdown one node, so one kafka broker and one streaming app is down
> now i see exceptions in other two streaming apps and it never gets re
> balanced waited for hours and never comes back to norma
> is there anything am missing?
> i also tried looking into when one broker is down call stream.close, cleanup
> and restart this also doesn't help
> can anyone help me?
>
>
>
> One thing i observed lately is that kafka topics with partitions one gets
> reassigned but i have topics of 16 partitions and replication factor 3. It
> never settles up
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
