hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ashu Pachauri (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HBASE-17117) Reversed scan returns deleted versions and breaks RegionLocator
Date Thu, 05 Oct 2017 19:07:01 GMT

     [ https://issues.apache.org/jira/browse/HBASE-17117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Ashu Pachauri resolved HBASE-17117.
    Resolution: Cannot Reproduce

After multiple attempts, we could not reproduce this issue. Going close this due to lack of
any further details.

> Reversed scan returns deleted versions and breaks RegionLocator
> ---------------------------------------------------------------
>                 Key: HBASE-17117
>                 URL: https://issues.apache.org/jira/browse/HBASE-17117
>             Project: HBase
>          Issue Type: Bug
>          Components: Scanners
>    Affects Versions: 1.3.0
>            Reporter: Ashu Pachauri
>             Fix For: 1.3.2
>         Attachments: reverseScanMetaDeleteFamily.txt
> We started seeing clients persistently throwing errors as they were trying to talk to
a region that was non existent (split a few days ago). We verified that the region was deleted
from meta when the split happened.
> On performing a raw scan on meta, the deleted version for the split region appears, which
also does on performing a normal reversed scan. Since MetaScanner uses a reversed scan, this
explains why clients see non existent regions.
> We also verified that there was no in-memory corrupt state by failing over the master.
When we trigger major compaction on meta, the problem goes away further confirming the fact
that we were seeing deleted versions.

This message was sent by Atlassian JIRA

View raw message