You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@kafka.apache.org by GitBox <gi...@apache.org> on 2021/05/03 16:57:30 UTC

[GitHub] [kafka] wenbingshen removed a comment on pull request #10617: KAFKA-12734: LazyTimeIndex & LazyOffsetIndex may cause niobufferoverflow when skip activeSegment sanityCheck

wenbingshen removed a comment on pull request #10617:
URL: https://github.com/apache/kafka/pull/10617#issuecomment-831393455


   > @wenbingshen : It would be useful to be clear what the PR wants to address. To me, if the index is corrupted because of our recovery logic (e.g., not handling cleaning shutdown file properly), we should just fix the cause. It's possible that after a clean restart, the index is corrupted due to storage issues. In that case, validating the index when the index is opened could potentially be useful. If we want to do that, it seems that we should we just do the validation on every index open, instead of just for the active segment?
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to 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