[
https://issues.apache.org/jira/browse/NIFI-4623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16261093#comment-16261093
]
ASF subversion and git services commented on NIFI-4623:
-------------------------------------------------------
Commit e8b2387cb29ed35e5819ac8cf95af7cf020bbc7a in nifi's branch
refs/heads/master from [~jwoschitz]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=e8b2387 ]
NIFI-4623: This closes #2281. Removed obsolete instability warning in
documentation of newer (>= 0_10) Kafka processors
Signed-off-by: joewitt <joew...@apache.org>
> Remove obsolete instability warning in documentation of newer (>= 0_10) Kafka
> processors
> ----------------------------------------------------------------------------------------
>
> Key: NIFI-4623
> URL: https://issues.apache.org/jira/browse/NIFI-4623
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Documentation & Website
> Affects Versions: 1.4.0
> Reporter: Janosch Woschitz
> Priority: Minor
> Labels: documentation
>
> The documentation of all Kafka processors (publish and consume) does contain
> the following warning:
> {quote}Please note there are cases where the publisher can get into an
> indefinite stuck state. We are closely monitoring how this evolves in the
> Kafka community and will take advantage of those fixes as soon as we can. In
> the meantime it is possible to enter states where the only resolution will be
> to restart the JVM NiFi runs on.{quote}
> Based on a conversation on the dev mailing list, Joe Witt stated that this
> warning is not needed anymore for processors targeting Kafka 0_10 and beyond:
> {quote}It was there previously because it
> was observed that timeout conditions could cause threads to stay in a
> hung state and as the caller of the client we weren't in a position to
> resolve it. However, newer client libraries are better and I no
> longer have observed these issues personally. For the 0_10 or newer
> clients I think we can adjust the docs to indicate that these should
> work just fine.{quote}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
