You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Ray Chiang (JIRA)" <ji...@apache.org> on 2018/07/19 20:09:00 UTC
[jira] [Updated] (KAFKA-6939) Change the default of
log.message.timestamp.difference.max.ms to 500 years
[ https://issues.apache.org/jira/browse/KAFKA-6939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ray Chiang updated KAFKA-6939:
------------------------------
Component/s: log
> Change the default of log.message.timestamp.difference.max.ms to 500 years
> --------------------------------------------------------------------------
>
> Key: KAFKA-6939
> URL: https://issues.apache.org/jira/browse/KAFKA-6939
> Project: Kafka
> Issue Type: Improvement
> Components: log
> Reporter: Badai Aqrandista
> Priority: Minor
>
> If producer incorrectly provides timestamp in microsecond (not in millisecond), the record is accepted by default and can cause broker to roll the segment files continuously. And on a heavily used broker, this will generate a lot of index files, which then causes the broker to hit `vm.max_map_count`.
> So I'd like to suggest changing the default for log.message.timestamp.difference.max.ms to 15768000000000 (500 years * 365 days * 86400 seconds * 1000). This would reject timestamp in microsecond from producer and still allow most historical data to be stored in Kafka.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)