[
https://issues.apache.org/jira/browse/NIFI-3189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15878238#comment-15878238
]
ASF GitHub Bot commented on NIFI-3189:
--------------------------------------
Github user ijokarumawak commented on the issue:
https://github.com/apache/nifi/pull/1527
Dear reviewers,
This PR contains handful debug level logs that would make easier to
understand how the additional thread is working. To see those log messages,
modify `conf/logback.xml` as follows:
```xml
<logger name="org.apache.nifi" level="INFO"/>
<logger name="org.apache.nifi.processors" level="WARN"/>
<!-- Add this line -->
<logger name="org.apache.nifi.processors.kafka.pubsub" level="DEBUG" />
<logger name="org.apache.nifi.processors.standard.LogAttribute"
level="INFO"/>
<logger name="org.apache.nifi.controller.repository.StandardProcessSession"
level="WARN" />
```
This PR is aimed for ConsumeKafka_0_10. Once this is proved to work
properly, I'll create another PR for ConsumeKafka (0.9) similarly.
Thanks a lot in advance!
> 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
>
> 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)
