[
https://issues.apache.org/jira/browse/KAFKA-5426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16046495#comment-16046495
]
Paolo Patierno commented on KAFKA-5426:
---------------------------------------
Hi,
the linger.ms parameter is set using the `--timeout` option on the command line
which if not specified is 1000 ms.
At same time the batch.size parameter is set using the
`--max-partition-memory-bytes` option on the command line which if not
specified is 16384.
It means that even if you specify linger.ms and batch.size using
--producer-property or --producer.config, they will be always overwritten by
the above "specific" options.
> One second delay in kafka-console-producer
> ------------------------------------------
>
> Key: KAFKA-5426
> URL: https://issues.apache.org/jira/browse/KAFKA-5426
> Project: Kafka
> Issue Type: Bug
> Components: config, producer
> Affects Versions: 0.10.2.1
> Environment: Ubuntu 16.04 with OpenJDK-8 and Ubuntu 14.04 with
> OpenJDK-7
> Reporter: Francisco
> Priority: Minor
> Original Estimate: 3h
> Remaining Estimate: 3h
>
> Hello!
> I have been trying to change the default delay for the original
> kafka-console-producer with both adding the producer.properties with a
> different configuration for linger.ms and batch.size, and also providing it
> directly in the command line with "--property" but nothing works.
> I have also tried it in a VM with Ubuntu 14.04 and using 0.8.2.1 Kafka
> version but I have had the same result. I don't know if it has been designed
> like that to don't be able to change the behaviour of the console-producer or
> if this is a bug.
> Here you can see my original post in StackOverFlow asking for help in this
> issue:
> https://stackoverflow.com/questions/44334304/kafka-spark-streaming-constant-delay-of-1-second
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
