[
https://issues.apache.org/jira/browse/HBASE-17343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai updated HBASE-17343:
-----------------------------------
Attachment: ut.v1.patch
bq. Do we have a new issue for the compacting memstore problem? Or all in one
patch?
in one patch
bq. I do not understand why do you say that the problem there is related
specifically to CompactingMemStore
Please see TestStore#testCreateScannerAndSnapshotConcurrently in ut.v1.patch
bq. Can you please explain?
We will lose the latest active segment when creating the scanner with the
following execution order.
# List<? extends Segment> pipelineList = pipeline.getSegments(); // getScanners
# List<? extends Segment> snapshotList = snapshot.getAllSegments(); //
getScanners
# pipeline.pushHead(active); // snapshot
# resetActive(); // snapshot
# order = addToScanners(active, readPt, order, list); // getScanners
Therefore, we should cache the active segment before getting the segments from
pipeline. The side-effect is that we may have duplicate scanner but the
scenario is rare and should be tolerated for ACID.
> Make Compacting Memstore default in 2.0 with BASIC as the default type
> ----------------------------------------------------------------------
>
> Key: HBASE-17343
> URL: https://issues.apache.org/jira/browse/HBASE-17343
> Project: HBase
> Issue Type: New Feature
> Components: regionserver
> Affects Versions: 2.0.0
> Reporter: ramkrishna.s.vasudevan
> Assignee: Anastasia Braginsky
> Priority: Blocker
> Fix For: 2.0.0
>
> Attachments: HBASE-17343-V01.patch, HBASE-17343-V02.patch,
> HBASE-17343-V04.patch, HBASE-17343-V05.patch, HBASE-17343-V06.patch,
> HBASE-17343-V07.patch, HBASE-17343-V08.patch, HBASE-17343-V09.patch,
> ut.v1.patch
>
>
> FYI [~anastas], [~eshcar] and [~ebortnik].
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
