You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Jason Gustafson (JIRA)" <ji...@apache.org> on 2017/12/20 18:37:00 UTC
[jira] [Created] (KAFKA-6392) Do not permit message down-conversion
for replicas
Jason Gustafson created KAFKA-6392:
--------------------------------------
Summary: Do not permit message down-conversion for replicas
Key: KAFKA-6392
URL: https://issues.apache.org/jira/browse/KAFKA-6392
Project: Kafka
Issue Type: Improvement
Reporter: Jason Gustafson
We have seen several cases where down-conversion caused replicas to diverge from the leader in subtle ways. Generally speaking, even if we addressed all of the edge cases so that down-conversion worked correctly as far as consistency of offsets, it would probably still be a bad idea to permit down-conversion. For example, this can cause message timestamps to be lost if down-converting from v1 to v0, or transactional data could be lost if down-converting from v2 to v1 or v0.
With that in mind, it would better to forbid down-conversion for replica fetches. Following the normal upgrade procedure, down-conversion is not needed anyway, but users often skip updating the inter-broker version. It is probably better in these cases to let the ISR shrink until the replicas have been updated as well.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)