[ 
https://issues.apache.org/jira/browse/HBASE-14921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

stack updated HBASE-14921:
--------------------------
    Release Note: 
A long, working issue that discussed Segment formats introducing CellArrayMap 
(delivered as the patch attached to this issue) and CellChunkMap (to be 
delivered later in HBASE-16421 but see patch v02 for an embryonic form named 
CellBlockSerialized); when to copy Segment data (and when not too); and then 
what to include at flush time (the suffix Segment or all Segments). Designs 
that evolved as discussion went on are attached. Outstanding issues turned up 
here, not including a CellChunkMap implementation, are listed below but are to 
be addressed in follow-ons:

1. The flattening without compaction is causing many small segments in 
pipeline, and they are not flushed all together.
2. The issue of compaction prediction cost.

> Inmemory Compaction optimizations
> ---------------------------------
>
>                 Key: HBASE-14921
>                 URL: https://issues.apache.org/jira/browse/HBASE-14921
>             Project: HBase
>          Issue Type: Sub-task
>    Affects Versions: 2.0.0
>            Reporter: Eshcar Hillel
>            Assignee: Anastasia Braginsky
>             Fix For: 2.0.0
>
>         Attachments: CellBlocksSegmentInMemStore.pdf, 
> CellBlocksSegmentinthecontextofMemStore(1).pdf, HBASE-14921-V01.patch, 
> HBASE-14921-V02.patch, HBASE-14921-V03.patch, HBASE-14921-V04-CA-V02.patch, 
> HBASE-14921-V04-CA.patch, HBASE-14921-V05-CAO.patch, 
> HBASE-14921-V06-CAO.patch, HBASE-14921-V08-CAO.patch, 
> HBASE-14921-V09-CAO.patch, HBASE-14921-V10-CAO.patch, 
> HBASE-14921-V11-CAO.patch, HBASE-14921-V11-CAO.patch, 
> HBASE-14921-V12-CAO.patch, InitialCellArrayMapEvaluation.pdf, 
> IntroductiontoNewFlatandCompactMemStore.pdf, MemStoreSizes.pdf, 
> MemstoreItrCountissue.patch, NewCompactingMemStoreFlow.pptx
>
>
> Memory optimizations including compressed format representation and offheap 
> allocations



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to