[
https://issues.apache.org/jira/browse/NIFI-3189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15882193#comment-15882193
]
ASF GitHub Bot commented on NIFI-3189:
--------------------------------------
Github user ijokarumawak commented on the issue:
https://github.com/apache/nifi/pull/1527
@bbende Thanks for reviewing. Incorporated comment. While I was doing so, I
found that Kafka client library started supporting heartbeat in background
thread [KAFKA-3888](https://issues.apache.org/jira/browse/KAFKA-3888) since
0.10.1.0.
Maybe we should test the latest Kafka client, that may automatically solve
this issue without any modification on NiFi side, although I haven't looked at
the new client code yet. If it does, this PR will be purely for ConsumeKafka
(0.9).
> ConsumeKafka 0.9 and 0.10 can cause consumer rebalance when backpressure is
> engaged
> -----------------------------------------------------------------------------------
>
> Key: NIFI-3189
> URL: https://issues.apache.org/jira/browse/NIFI-3189
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 1.1.0
> Reporter: Joseph Witt
> Assignee: Koji Kawamura
>
> ConsumeKafka processors can alert to rebalance issues when backpressure is
> engaged on the output connection and is then freed up. This is because we're
> not doing anything with those consumers for a period of time and the kafka
> client detects this and initiates a rebalance. We should ensure that even
> when we cannot send more data due to back pressure that we at least have some
> sort of keep alive behavior with the kafka client. Or, if that isn't an
> option we should at least document the situation.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
