[
https://issues.apache.org/jira/browse/KAFKA-4340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-4340.
--------------------------------
Resolution: Won't Fix
Compacted topics means that we would also need KAFKA-4907 to avoid rejecting
messages where log.retention.ms doesn't apply. Implementing that makes things
more complex and [~junrao] suggested that it may be better to change the
default of `message.timestamp.difference.max.ms` back to Long.MaxValue. That's
being tracked via KAFKA-5344 so I'm closing this as "Won't fix". Note that we
will keep the warning that was introduced in case frequent log rolling is
likely to happen due to the configuration.
> 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
>
> [~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)
