You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "shilin Lu (Jira)" <ji...@apache.org> on 2019/11/07 09:56:00 UTC
[jira] [Updated] (KAFKA-9156) LazyTimeIndex & LazyOffsetIndex may
cause niobufferoverflow in concurrent state
[ https://issues.apache.org/jira/browse/KAFKA-9156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
shilin Lu updated KAFKA-9156:
-----------------------------
Reviewer: Ismael Juma
> LazyTimeIndex & LazyOffsetIndex may cause niobufferoverflow in concurrent state
> -------------------------------------------------------------------------------
>
> Key: KAFKA-9156
> URL: https://issues.apache.org/jira/browse/KAFKA-9156
> Project: Kafka
> Issue Type: Bug
> Components: core
> Affects Versions: 2.3.0
> Reporter: shilin Lu
> Priority: Critical
> Attachments: image-2019-11-07-17-42-13-852.png, image-2019-11-07-17-44-05-357.png, image-2019-11-07-17-46-53-650.png
>
>
> !image-2019-11-07-17-42-13-852.png!
> this timeindex get function is not thread safe ,may cause create some timeindex.
> !image-2019-11-07-17-44-05-357.png!
> When create timeindex not exactly one ,may cause mappedbytebuffer position to end. Then write index entry to this mmap file will cause java.nio.BufferOverflowException.
>
> !image-2019-11-07-17-46-53-650.png!
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)