You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@kafka.apache.org by "Jiangjie Qin (JIRA)" <ji...@apache.org> on 2017/05/29 06:33:04 UTC

[jira] [Updated] (KAFKA-5344) Change message.timestamp.difference.max.ms back to Long.MaxValue

     [ https://issues.apache.org/jira/browse/KAFKA-5344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jiangjie Qin updated KAFKA-5344:
--------------------------------
    Status: Patch Available  (was: Open)

> Change message.timestamp.difference.max.ms back to Long.MaxValue
> ----------------------------------------------------------------
>
>                 Key: KAFKA-5344
>                 URL: https://issues.apache.org/jira/browse/KAFKA-5344
>             Project: Kafka
>          Issue Type: Bug
>          Components: core
>            Reporter: Jiangjie Qin
>            Assignee: Jiangjie Qin
>             Fix For: 0.11.0.0
>
>
> Per discussion in KAFKA-4340 and PR-2705 (https://github.com/apache/kafka/pull/2705), we agreed it is easier to just set the default value of message.timestamp.difference.max.ms back to Long.MaxValue. User can override it to avoid frequent rolling if needed.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)