[
https://issues.apache.org/jira/browse/HBASE-16417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15906123#comment-15906123
]
Edward Bortnikov commented on HBASE-16417:
------------------------------------------
.. So [~eshcar] answered nearly all of it here .. A couple of small remarks.
The expected number of 2 segments in the pipeline follows from the fact that
disk flush normally happens when there are 4. Assuming we are growing from 0,
the expectation is 2.
The varying WAL size with Async WAL introduces much noise indeed. However,
please note that the overall volume of WAL writes differs between Sync and
Async without one line of Accordion involved, why does this happen with the
same workload? (Note that with Sync, the WAL volume is the same no matter what
type of in-memory compaction is used). Looking forward to some help here :)
> In-Memory MemStore Policy for Flattening and Compactions
> --------------------------------------------------------
>
> Key: HBASE-16417
> URL: https://issues.apache.org/jira/browse/HBASE-16417
> Project: HBase
> Issue Type: Sub-task
> Reporter: Anastasia Braginsky
> Assignee: Eshcar Hillel
> Fix For: 2.0.0
>
> Attachments: HBASE-16417-benchmarkresults-20161101.pdf,
> HBASE-16417-benchmarkresults-20161110.pdf,
> HBASE-16417-benchmarkresults-20161123.pdf,
> HBASE-16417-benchmarkresults-20161205.pdf,
> HBASE-16417-benchmarkresults-20170309.pdf
>
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
