[
https://issues.apache.org/jira/browse/KAFKA-596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapnil Ghike updated KAFKA-596:
--------------------------------
Attachment: kafka-596-v3.patch
After a discussion with Jun, reverted the conditions in maybeRoll() to the
trunk version.
Setting firstAppendTime to None in LogSegment.truncateTo() when messageSet size
becomes 0 is enough to make sure that Log.maybeRoll() will not roll a new
segment at the same starting offset as the last segment.
> LogSegment.firstAppendTime not reset after truncate to
> ------------------------------------------------------
>
> Key: KAFKA-596
> URL: https://issues.apache.org/jira/browse/KAFKA-596
> Project: Kafka
> Issue Type: Bug
> Components: core
> Affects Versions: 0.8
> Reporter: Jun Rao
> Assignee: Swapnil Ghike
> Labels: bugs
> Attachments: kafka-596.patch, kafka-596-v2.patch, kafka-596-v3.patch
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> Currently, we don't reset LogSegment.firstAppendTime after the segment is
> truncated. What can happen is that we truncate the segment to size 0 and on
> next append, a new log segment with the same starting offset is rolled
> because the time-based rolling is triggered.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
