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

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 0.10.1.0
• Component/s: core
• Assignee: Jiangjie Qin
• Reporter: Jiangjie Qin
• Created: 25/Oct/16 01:47
• Updated: 30/May/17 14:48
• Resolved: 30/May/17 14:48

Description

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.

Issue Links

• is related to: KAFKA-4907 compacted topic shouldn't reject messages with old timestamp
• is related to: KAFKA-5344 Change message.timestamp.difference.max.ms back to Long.MaxValue
• links to: GitHub Pull Request #2071