[
https://issues.apache.org/jira/browse/KAFKA-1641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14977958#comment-14977958
]
Denis Zhdanov commented on KAFKA-1641:
--------------------------------------
Ah, according to Github and release plan 0.9.0 is planned for Nov 2015 and no
releases planned for 0.8.x *sigh*
> Log cleaner exits if last cleaned offset is lower than earliest offset
> ----------------------------------------------------------------------
>
> Key: KAFKA-1641
> URL: https://issues.apache.org/jira/browse/KAFKA-1641
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 0.8.1.1
> Reporter: Joel Koshy
> Assignee: Guozhang Wang
> Fix For: 0.9.0.0
>
> Attachments: KAFKA-1641.patch, KAFKA-1641_2014-10-09_13:04:15.patch
>
>
> Encountered this recently: the log cleaner exited a while ago (I think
> because the topic had compressed messages). That issue was subsequently
> addressed by having the producer only send uncompressed. However, on a
> subsequent restart of the broker we see this:
> In this scenario I think it is reasonable to just emit a warning and have the
> cleaner round up its first dirty offset to the base offset of the first
> segment.
> {code}
> [kafka-server] [] [kafka-log-cleaner-thread-0], Error due to
> java.lang.IllegalArgumentException: requirement failed: Last clean offset is
> 54770438 but segment base offset is 382844024 for log testtopic-0.
> at scala.Predef$.require(Predef.scala:145)
> at kafka.log.Cleaner.buildOffsetMap(LogCleaner.scala:491)
> at kafka.log.Cleaner.clean(LogCleaner.scala:288)
> at
> kafka.log.LogCleaner$CleanerThread.cleanOrSleep(LogCleaner.scala:202)
> at kafka.log.LogCleaner$CleanerThread.doWork(LogCleaner.scala:187)
> at kafka.utils.ShutdownableThread.run(ShutdownableThread.scala:51)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
