[
https://issues.apache.org/jira/browse/KAFKA-4099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jiangjie Qin updated KAFKA-4099:
--------------------------------
Description: 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. (was: 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.)
> 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)
