[jira] [Comment Edited] (KAFKA-4340) Change the default value of log.message.timestamp.difference.max.ms to the same as log.retention.ms

["Jiangjie Qin (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/KAFKA-4340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15868777#comment-15868777 ] 

Jiangjie Qin edited comment on KAFKA-4340 at 2/15/17 11:05 PM:
---------------------------------------------------------------

[~junrao] [~ijuma] [~cmccabe] I created https://github.com/apache/kafka/pull/2544 for this. I am run the branch builder now.


was (Author: becket_qin):
[~junrao] [~ijuma] [~cmccabe] I created https://github.com/apache/kafka/pull/2071 for this. I am run the branch builder now.

> 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.3.0
>
>
> [~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.15#6346)