[
https://issues.apache.org/jira/browse/HBASE-14919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15092051#comment-15092051
]
Eshcar Hillel commented on HBASE-14919:
---------------------------------------
I am not sure how updateLowestUnflushedSequenceIdInWal is related to
HBASE-15082, I might be missing some context. Can you elaborate [~anoop.hbase]?
The motivation behind updateLowestUnflushedSequenceIdInWal is to have the WAL
cover all entries still in memory (this is required for correctness) while
truncating the WAL so it does not get too long (to bound MTTR). It is required
for compacting memstore which cherry picks entries to be removed from memory
without flushing them to disk. Since this is done in the background and not in
a batched mode, the new method is invoked whenever needs to update the wal.
> Infrastructure refactoring
> --------------------------
>
> Key: HBASE-14919
> URL: https://issues.apache.org/jira/browse/HBASE-14919
> Project: HBase
> Issue Type: Sub-task
> Affects Versions: 2.0.0
> Reporter: Eshcar Hillel
> Assignee: Eshcar Hillel
> Attachments: HBASE-14919-V01.patch, HBASE-14919-V01.patch,
> HBASE-14919-V02.patch, HBASE-14919-V03.patch, HBASE-14919-V04.patch,
> HBASE-14919-V04.patch
>
>
> Refactoring the MemStore hierarchy, introducing segment (StoreSegment) as
> first-class citizen and decoupling memstore scanner from the memstore
> implementation.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
