kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Gustafson (JIRA)" <j...@apache.org>
Subject [jira] [Created] (KAFKA-7897) Invalid use of epoch cache following message format downgrade
Date Tue, 05 Feb 2019 01:20:00 GMT
Jason Gustafson created KAFKA-7897:
--------------------------------------

             Summary: Invalid use of epoch cache following message format downgrade
                 Key: KAFKA-7897
                 URL: https://issues.apache.org/jira/browse/KAFKA-7897
             Project: Kafka
          Issue Type: Bug
            Reporter: Jason Gustafson
            Assignee: Jason Gustafson


Message format downgrades are not supported, but they generally work as long as broker/clients
at least can continue to parse both message formats. After a downgrade, the truncation logic
should revert to using the high watermark, but currently we use the existence of any cached
epoch as the requirement in order to leverage OffsetsForLeaderEpoch. This has the effect of
causing a massive truncation after startup which causes re-replication.

I think our options to fix this are to either 1) clear the cache when we notice a downgrade,
or 2) forbid downgrades and raise an error.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message