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-18638) The old cells will return to client if the new cells are deleted
Date Mon, 21 Aug 2017 19:45:01 GMT

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

Chia-Ping Tsai commented on HBASE-18638:

I'm confused about the ttl. Can the cells having ttl cover the old cell? If all cells are
in-memory, the cells which expire won't cover any old cells (The old cells can be given back
to client). However, the cells which don't expire will make flusher drop the old cells. That
inconsistency introduce sort of time-based dirty data.
[~anoop.hbase] Is it also a known issue in HBase? I hope the version-related inconsistency
can be resolved here.

> The old cells will return to client if the new cells are deleted
> ----------------------------------------------------------------
>                 Key: HBASE-18638
>                 URL: https://issues.apache.org/jira/browse/HBASE-18638
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 1.3.1, 1.2.6, 2.0.0-alpha-1
>            Reporter: Chia-Ping Tsai
>            Assignee: Chia-Ping Tsai
>            Priority: Critical
>             Fix For: 2.0.0, 1.4.0, 1.3.2, 1.5.0, 1.2.7
>         Attachments: HBASE-18638-ut.patch, HBASE-18638-ut.patch
> |put_0(t0)|
> |put_1(t1)|  <-- the latest cell
> If we call get, the put_1 will return. That is good.
> If we call get after a delete, the put_0 will return. That is weird. The put_0 is old
data, and it should be dropped in flush. For client, put_0 should not exist after the put_1

This message was sent by Atlassian JIRA

View raw message