You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2015/10/03 00:11:26 UTC
[jira] [Commented] (NIFI-1020) Upgrade to Kafka 0.8.2 client
library to alleviate partition stickiness
[ https://issues.apache.org/jira/browse/NIFI-1020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14941860#comment-14941860 ]
ASF GitHub Bot commented on NIFI-1020:
--------------------------------------
GitHub user randerzander opened a pull request:
https://github.com/apache/nifi/pull/99
NIFI-1020
Bumping Kafka API version to prevent PutKafka from writing to only one partition.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/randerzander/nifi master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/99.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #99
----
commit da907d3d94b594e59859f1906a967fac5b0eba0c
Author: Randy Gelhausen <rg...@gmail.com>
Date: 2015-10-02T22:09:02Z
Bumped nifi-kafka-processors Kafka version
----
> Upgrade to Kafka 0.8.2 client library to alleviate partition stickiness
> -----------------------------------------------------------------------
>
> Key: NIFI-1020
> URL: https://issues.apache.org/jira/browse/NIFI-1020
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Affects Versions: 0.3.0
> Reporter: Aldrin Piri
>
> The default partitioning scheme introduced in Kafka 0.8.1 led to a bug/feature that aided in keeping number of open socket connections low. Additional information can be found: https://cwiki.apache.org/confluence/display/KAFKA/FAQ#FAQ-Whyisdatanotevenlydistributedamongpartitionswhenapartitioningkeyisnotspecified?
> This was addressed in the Java clients for 0.8.2 which is listed as being compatible with any 0.8.x release.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)