You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Jason Gustafson (JIRA)" <ji...@apache.org> on 2016/10/13 04:32:20 UTC
[jira] [Updated] (KAFKA-4298) LogCleaner does not convert
compressed message sets properly
[ https://issues.apache.org/jira/browse/KAFKA-4298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason Gustafson updated KAFKA-4298:
-----------------------------------
Description: When cleaning the log, we attempt to write the cleaned messages using the message format configured for the topic, but as far as I can tell, we do not convert the wrapped messages in compressed message sets. For example, if there is an old compressed message set with magic=0 in the log and the topic is configured for magic=1, then after cleaning, the new message set will have a wrapper with magic=1, but the nested messages will still have magic=0. If this happens, there does not seem to be an easy way to recover without manually fixing up the log. (was: When cleaning the log, we attempt to write the cleaned messages using the message format configured for the topic, but as far as I can tell, we do not convert the wrapped messages in compressed message sets. For example, if there is an old compressed message set with magic=0 in the log and the topic is configured for magic=1, then after cleaning, the new message set will have a wrapper with magic=1, but the nested messages will still have magic=0. If this happens, there does not seem to be an easy way to recover with manually fixing up the log.)
> LogCleaner does not convert compressed message sets properly
> ------------------------------------------------------------
>
> Key: KAFKA-4298
> URL: https://issues.apache.org/jira/browse/KAFKA-4298
> Project: Kafka
> Issue Type: Bug
> Reporter: Jason Gustafson
> Assignee: Jason Gustafson
> Priority: Critical
> Fix For: 0.10.1.1
>
>
> When cleaning the log, we attempt to write the cleaned messages using the message format configured for the topic, but as far as I can tell, we do not convert the wrapped messages in compressed message sets. For example, if there is an old compressed message set with magic=0 in the log and the topic is configured for magic=1, then after cleaning, the new message set will have a wrapper with magic=1, but the nested messages will still have magic=0. If this happens, there does not seem to be an easy way to recover without manually fixing up the log.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)