[
https://issues.apache.org/jira/browse/HBASE-18375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16140311#comment-16140311
]
Andrew Purtell commented on HBASE-18375:
----------------------------------------
[~anastas] This is a hacky suggestion, but if 'HBASE-18375-branch-2.patch'
worked earlier, use it again. Attach the new patch using the same name. JIRA
sorts patches by most recent so as long as hadoopqa does the right thing by
choosing the first in the list, it will work. As a last resort, if you think
hadoopqa isn't picking up the latest (although I believe it does), delete the
previously attached branch-2 patches and then attach only the latest.
> 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-branch-2.patch, HBASE-18375-V01.patch,
> HBASE-18375-V02-branch-2.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)
