[
https://issues.apache.org/jira/browse/HBASE-18375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16134016#comment-16134016
]
Anastasia Braginsky commented on HBASE-18375:
---------------------------------------------
[~anoop.hbase] and [~ram_krish] thank you for your help and reviews!
Anoop, Ram and [~stack], what about committing to Release 2.0 as well? If it is
needed, what branch should be used?
In Release 2.0 the MSLAB chunks may not return to the pool, but with low
probability of this to happen.
> The pool chunks from ChunkCreator are deallocated while in pool because there
> is no reference to them
> -----------------------------------------------------------------------------------------------------
>
> Key: HBASE-18375
> URL: https://issues.apache.org/jira/browse/HBASE-18375
> Project: HBase
> Issue Type: Sub-task
> Affects Versions: 2.0.0-alpha-1
> Reporter: Anastasia Braginsky
> Assignee: Anastasia Braginsky
> Priority: Critical
> Fix For: 2.0.0
>
> Attachments: HBASE-18375-V01.patch, HBASE-18375-V02.patch,
> HBASE-18375-V03.patch, HBASE-18375-V04.patch, HBASE-18375-V05.patch,
> HBASE-18375-V06.patch, HBASE-18375-V07.patch, HBASE-18375-V08.patch,
> HBASE-18375-V09.patch, HBASE-18375-V10.patch, HBASE-18375-V11.patch
>
>
> Because MSLAB list of chunks was changed to list of chunk IDs, the chunks
> returned back to pool can be deallocated by JVM because there is no reference
> to them. The solution is to protect pool chunks from GC by the strong map of
> ChunkCreator introduced by HBASE-18010. Will prepare the patch today.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
