You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2019/02/22 22:57:00 UTC

[jira] [Commented] (KAFKA-7959) Clear/delete epoch cache if old message format is in use

    [ https://issues.apache.org/jira/browse/KAFKA-7959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16775669#comment-16775669 ] 

ASF GitHub Bot commented on KAFKA-7959:
---------------------------------------

hachikuji commented on pull request #6298: KAFKA-7959: Delete leader epoch cache files with old message format versions
URL: https://github.com/apache/kafka/pull/6298
 
 
   
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> Clear/delete epoch cache if old message format is in use
> --------------------------------------------------------
>
>                 Key: KAFKA-7959
>                 URL: https://issues.apache.org/jira/browse/KAFKA-7959
>             Project: Kafka
>          Issue Type: Bug
>            Reporter: Jason Gustafson
>            Assignee: Stanislav Kozlovski
>            Priority: Major
>
> Because of KAFKA-7897, it is possible to have a sparse epoch cache when using the old message format. The fix for that issue addresses the problem of improper use of that cache while the message format remains on an older version. However, it leaves the possibility of misuse during a message format upgrade, which can cause unexpected truncation and re-replication. To fix the problem, we should delete or at least clear the cache whenever the old message format is used.
> Note that this problem was fixed unintentionally in 2.1 with the patch for KAFKA-7897. This issue applies specifically to the 2.0 branch.



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