[
https://issues.apache.org/jira/browse/HBASE-17081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15747604#comment-15747604
]
Edward Bortnikov commented on HBASE-17081:
------------------------------------------
Re/ [~stack]'s question about what's next:
1. HBASE-17294 configuration (Eshcar) - committed, thanks [~stack].
2. HBASE-16851 documentation (me) - need to complete 3 blog posts: (1) user
manual - complete, give or take, (2) performance eval, and (3) programmer's
manual. Where should we post all those? Apache blog?
3. HBASE-16417 (Eshcar) automated policy for figuring out whether the BASIC or
the EAGER algorithm is to be used. Small refactoring the internal API for
future policies.
Independent on in-memory compaction per se:
1. HBASE-16421 CellChunkMap implementation (Anastasia) - starting now, need to
coordinate with [~anoop.hbase] and [~ram_krish].
2. JIRA TBD Memstore-First Get (Eshcar) - Big value demonstrated by benchmarks
in HBASE-16851, we should try to implement & push before 2.0 closes.
Sounds like a plan (smile) ?
> Flush the entire CompactingMemStore content to disk
> ---------------------------------------------------
>
> Key: HBASE-17081
> URL: https://issues.apache.org/jira/browse/HBASE-17081
> Project: HBase
> Issue Type: Sub-task
> Reporter: Anastasia Braginsky
> Assignee: Anastasia Braginsky
> Attachments: HBASE-15787_8.patch, HBASE-17081-V01.patch,
> HBASE-17081-V02.patch, HBASE-17081-V03.patch, HBASE-17081-V04.patch,
> HBASE-17081-V05.patch, HBASE-17081-V06.patch, HBASE-17081-V06.patch,
> HBaseMeetupDecember2016-V02.pptx, Pipelinememstore_fortrunk_3.patch
>
>
> Part of CompactingMemStore's memory is held by an active segment, and another
> part is divided between immutable segments in the compacting pipeline. Upon
> flush-to-disk request we want to flush all of it to disk, in contrast to
> flushing only tail of the compacting pipeline.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
