[
https://issues.apache.org/jira/browse/KAFKA-4099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15454198#comment-15454198
]
ASF GitHub Bot commented on KAFKA-4099:
---------------------------------------
GitHub user becketqin opened a pull request:
https://github.com/apache/kafka/pull/1809
KAFKA-4099: Fix the potential frequent log rolling
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/becketqin/kafka KAFKA-4099
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/1809.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1809
----
commit 06b9548feaa68c5f224d56df5e1d35bb0287fc8c
Author: Jiangjie Qin <becket....@gmail.com>
Date: 2016-09-01T03:24:52Z
KAFKA-4099: Fix the potential frequent log rolling.
----
> Change the time based log rolling to only based on the message timestamp.
> -------------------------------------------------------------------------
>
> Key: KAFKA-4099
> URL: https://issues.apache.org/jira/browse/KAFKA-4099
> Project: Kafka
> Issue Type: Bug
> Components: core
> Reporter: Jiangjie Qin
> Assignee: Jiangjie Qin
> Fix For: 0.10.1.0
>
>
> This is an issue introduced in KAFKA-3163. When partition relocation occurs,
> the newly created replica may have messages with old timestamp and cause the
> log segment rolling for each message. The fix is to change the log rolling
> behavior to only based on the message timestamp when the messages are in
> message format 0.10.0 or above. If the first message in the segment does not
> have a timetamp, we will fall back to use the wall clock time for log rolling.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
