kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-5344) Change message.timestamp.difference.max.ms back to Long.MaxValue
Date Tue, 30 May 2017 14:56:04 GMT

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

ASF GitHub Bot commented on KAFKA-5344:
---------------------------------------

Github user asfgit closed the pull request at:

    https://github.com/apache/kafka/pull/3163


> 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.
> We will keep the warning that was introduced via KAFKA-4340 in case frequent log rolling
is likely to happen due to the configuration.



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

Mime
View raw message