[jira] Assigned: (HBASE-1761) getclosest doesn't understand delete family; manifests as "HRegionInfo was null or empty in .META" A.K.A the BS problem

["Jean-Daniel Cryans (JIRA)" <ji...@apache.org>]

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

Jean-Daniel Cryans reassigned HBASE-1761:
-----------------------------------------

    Assignee: stack

> getclosest doesn't understand delete family; manifests as "HRegionInfo was null or empty in .META" A.K.A the BS problem
> -----------------------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-1761
>                 URL: https://issues.apache.org/jira/browse/HBASE-1761
>             Project: Hadoop HBase
>          Issue Type: Bug
>            Reporter: stack
>            Assignee: stack
>             Fix For: 0.20.0
>
>         Attachments: 1761-v10.patch, 1761-v11.patch, 1761-v12.patch, 1761-v13.patch, 1761-v2.patch, 1761-v3.patch, 1761-v4.patch, 1761-v5.patch, 1761-v6.patch, 1761-v7.patch, 1761-v9.patch, 1761.patch
>
>
> getclosestatorbefore was not converted to deal with the new delete types.  It only knows how to process old style deletes.  Usually all is well as edits come in but its possible to get into state where you have persisted in one file a deletefamily for all in meta and in the file behind it, there are entries on the info family.  Since closest doesn't understand deletefamily, it will return the Put rows only for the subsequent getfull, which knows how to work with deletefamilies fail.
> Once this happens, table is hosed.  Seen on Bradford Stephens upload and at Powerset.  "Fix" is flush and major compact.  Gives impression that hbase is 'delicate'.  Fixing.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.