[
https://issues.apache.org/jira/browse/HBASE-17765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anastasia Braginsky updated HBASE-17765:
----------------------------------------
Release Note:
Reviving the merge of the compacting pipeline: making the limit on the number
of the segments in the pipeline configurable and adding the merge test.
In order to customize the pipeline size limit change the value of the
"hbase.hregion.compacting.pipeline.segments.limit" in the hbase-site.xml
Value 1 means to merge the segments on any flush-in-memory. Value higher than
16 means no merge.
was:Reviving the merge of the compacting pipeline: making the limit on the
number of the segments in the pipeline configurable, adding merge test, fixing
bug in sizes counting
> Reviving the merge possibility in the CompactingMemStore
> --------------------------------------------------------
>
> Key: HBASE-17765
> URL: https://issues.apache.org/jira/browse/HBASE-17765
> Project: HBase
> Issue Type: Sub-task
> Reporter: Anastasia Braginsky
> Assignee: Anastasia Braginsky
> Fix For: 2.0.0
>
> Attachments: HBASE-17765-V01.patch, HBASE-17765-V02.patch,
> HBASE-17765-V03.patch, HBASE-17765-V04.patch, HBASE-17765-V05.patch
>
>
> According to the new performance results presented in the HBASE-16417 we see
> that the read latency of the 90th percentile of the BASIC policy is too big
> due to the need to traverse through too many segments in the pipeline. In
> this JIRA we correct the bug in the merge sizing calculations and allow
> pipeline size threshold to be a configurable parameter.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
