[
https://issues.apache.org/jira/browse/SAMZA-546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14567247#comment-14567247
]
Robert Žuljević commented on SAMZA-546:
---------------------------------------
Hello,
I would like to start contributing to Samza and have chosen this task as my
"getting into" task. However, once I have located a suitable place to implement
the requested change(s). I've noticed the following comment, added in a commit
by yourself:
"DO NOT let caller to override these 2 configs for Kafka" (one of which is
indeed max.in.flight.requests.per.connection).
After reading through the e-mail thread I discovered that increasing
max.in.flight.requests.per.connection does not improve performance
significantly. My question is: Is this ticket still actual? : )
> Add config option max.in.flight.requests.per.connection
> -------------------------------------------------------
>
> Key: SAMZA-546
> URL: https://issues.apache.org/jira/browse/SAMZA-546
> Project: Samza
> Issue Type: Improvement
> Components: kafka
> Affects Versions: 0.8.0
> Reporter: Jordan Shaw
> Priority: Minor
> Labels: newbie
> Fix For: 0.10.0
>
>
> For higher throughput cases allow higher concurrency with the new Kafka
> producer via max.in.flight.requests.per.connection. Context on this
> discussion:
> http://mail-archives.apache.org/mod_mbox/samza-dev/201502.mbox/browser
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
