[
https://issues.apache.org/jira/browse/KAFKA-4340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15610518#comment-15610518
]
ASF GitHub Bot commented on KAFKA-4340:
---------------------------------------
GitHub user becketqin opened a pull request:
https://github.com/apache/kafka/pull/2071
KAFKA-4340: Change default message.timestamp.difference.max.ms to the same
as log.retention.ms
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/becketqin/kafka KAFKA-4340
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/2071.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 #2071
----
commit 5693cf603afdffe4d496596666de2a1d9b0faa9f
Author: Jiangjie Qin <becket....@gmail.com>
Date: 2016-10-27T03:05:52Z
KAFKA-4340: Change default message.timestamp.difference.max.ms to the same
as log.retention.ms
----
> Change the default value of log.message.timestamp.difference.max.ms to the
> same as log.retention.ms
> ---------------------------------------------------------------------------------------------------
>
> Key: KAFKA-4340
> URL: https://issues.apache.org/jira/browse/KAFKA-4340
> Project: Kafka
> Issue Type: Improvement
> Components: core
> Affects Versions: 0.10.1.0
> Reporter: Jiangjie Qin
> Assignee: Jiangjie Qin
> Fix For: 0.10.1.1
>
>
> [~junrao] brought up the following scenario:
> If users are pumping data with timestamp already passed log.retention.ms into
> Kafka, the messages will be appended to the log but will be immediately
> rolled out by log retention thread when it kicks in and the messages will be
> deleted.
> To avoid this produce-and-deleted scenario, we can set the default value of
> log.message.timestamp.difference.max.ms to be the same as log.retention.ms.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
