[
https://issues.apache.org/jira/browse/HBASE-16608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15531944#comment-15531944
]
Anoop Sam John commented on HBASE-16608:
----------------------------------------
Thanks for testing Ram.
bq.Also addIntoPooledChunks now adds from all the segments into one segment.
From each segment there is a chance the pooledChunk is full and you add all
those full chunkQueue to another chunkQueue which at the max can hold
chunkPool.getMaxCount().
Ya this is doing nothing with the pool as such. Each of the merged segments
might have N pooled chunks in its Q. Now we have merged all these segments
into one. We dont refer to those segments any more. So when the result segment
is getting closed some time later, we will have to release all of these chunks
to pool.. This op just put all PooledChunks from all these segments into one
Q. That is the Q in the result Segment. I dont think some thing wrong there.
> Introducing the ability to merge ImmutableSegments without copy-compaction or
> SQM usage
> ---------------------------------------------------------------------------------------
>
> Key: HBASE-16608
> URL: https://issues.apache.org/jira/browse/HBASE-16608
> Project: HBase
> Issue Type: Sub-task
> Reporter: Anastasia Braginsky
> Assignee: Anastasia Braginsky
> Attachments: HBASE-16417-V02.patch, HBASE-16417-V04.patch,
> HBASE-16417-V06.patch, HBASE-16417-V07.patch, HBASE-16417-V08.patch,
> HBASE-16417-V10.patch, HBASE-16608-V01.patch, HBASE-16608-V03.patch,
> HBASE-16608-V04.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
