[
https://issues.apache.org/jira/browse/SAMZA-546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14570118#comment-14570118
]
Navina Ramesh commented on SAMZA-546:
-------------------------------------
Hi Robert Žuljević,
Sorry for the late response. I had to read through the email thread to refresh
my memory :)
Configuring max.in.flight.requests.per.connection is supposed to improve
performance of the producer. However, it will not guarantee ordering. So, for
use-cases where there are no strict ordering requirements, this can be useful.
Currently, by default, we set max.in.flight.requests to 1 and retries to
integer max.
Which part of the email hinted that increasing
max.in.flight.requests.per.connection does not improve performance? I don't
think they even played around with that configuration. Am I missing something
here?
Imo, this ticket is valid as long as we can make sure that the user is aware of
the consequences of setting this value to greater than 1.
> 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)
