[
https://issues.apache.org/jira/browse/KAFKA-9156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16969720#comment-16969720
]
Guozhang Wang commented on KAFKA-9156:
--------------------------------------
[~lushilin] Thanks for reporting this ticket, and I think it is indeed an
issue: although Option is immutable we are trying to reassign the var. I think
we can fix it by replacing the `var Option` with a `val AtomicReference` in
which we can rely on `compareAndSet` to set the values atomically.
Would you like to provide a patch for it?
> 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)
