hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chia-Ping Tsai (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-17887) Row-level consistency is broken for read
Date Fri, 12 May 2017 10:32:04 GMT

    [ https://issues.apache.org/jira/browse/HBASE-17887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16007925#comment-16007925
] 

Chia-Ping Tsai commented on HBASE-17887:
----------------------------------------

bq. Was just saying an ideal and more efficient way with no unwanted new scanners and seeks.
The data had been copied from memstore to file when the update scanner op happen with updating
one new file. We could keep the scanner of older memstore(active, snapshot, pipeline) to avoid
seek but it is also dangerous because the GC won't release the memory of flushed data. Hence,
it seems to me that it is hard to save the cost of extra seek currently.


> Row-level consistency is broken for read
> ----------------------------------------
>
>                 Key: HBASE-17887
>                 URL: https://issues.apache.org/jira/browse/HBASE-17887
>             Project: HBase
>          Issue Type: Bug
>          Components: regionserver
>    Affects Versions: 2.0.0
>            Reporter: Umesh Agashe
>            Assignee: Chia-Ping Tsai
>            Priority: Blocker
>             Fix For: 2.0.0, 1.4.0, 1.2.6, 1.3.2, 1.4.1
>
>         Attachments: HBASE-17887.branch-1.v0.patch, HBASE-17887.branch-1.v1.patch, HBASE-17887.branch-1.v1.patch,
HBASE-17887.branch-1.v2.patch, HBASE-17887.branch-1.v2.patch, HBASE-17887.branch-1.v3.patch,
HBASE-17887.branch-1.v4.patch, HBASE-17887.branch-1.v4.patch, HBASE-17887.branch-1.v4.patch,
HBASE-17887.branch-1.v5.patch, HBASE-17887.branch-1.v6.patch, HBASE-17887.ut.patch, HBASE-17887.v0.patch,
HBASE-17887.v1.patch, HBASE-17887.v2.patch, HBASE-17887.v3.patch, HBASE-17887.v4.patch, HBASE-17887.v5.patch,
HBASE-17887.v5.patch
>
>
> As per the flaky tests dashboard here: https://builds.apache.org/job/HBASE-Find-Flaky-Tests/lastSuccessfulBuild/artifact/dashboard.html,
It fails 30% of the time.
> While working on HBASE-17863, a few verification builds on patch failed due to TestAcidGuarantees
didn't pass. IMHO, the changes for HBASE-17863 are unlikely to affect get/ put path.
> I ran the test with and without the patch several times locally and found that TestAcidGuarantees
fails without the patch similar number of times.
> Opening blocker, considering acid guarantees are critical to HBase.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message