[
https://issues.apache.org/jira/browse/HBASE-16195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15370378#comment-15370378
]
Anoop Sam John commented on HBASE-16195:
----------------------------------------
Ya, the code consider the customized flush size. I agree. My point is abt this
Q length calc
bq.int queueLength = conf.getInt(CHUNK_QUEUE_LENGTH, (int) (memstoreFlushSize /
chunkSize));
The default is calculated as flushSize/chunkSize.
The flush size what we got here is not a hard limit. The hard limit is the
blocking flush size which defaults to 4 times the flush size.
We wont need this change IMO. Both these jiras part of single bug. So any one
backporting this has to take both.
> Should not add chunk into chunkQueue if not using chunk pool in
> HeapMemStoreLAB
> -------------------------------------------------------------------------------
>
> Key: HBASE-16195
> URL: https://issues.apache.org/jira/browse/HBASE-16195
> Project: HBase
> Issue Type: Sub-task
> Reporter: Yu Li
> Assignee: Yu Li
> Attachments: HBASE-16195.patch, HBASE-16195_v2.patch,
> HBASE-16195_v3.patch
>
>
> Problem description and analysis please refer to HBASE-16193
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
