Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hbase-dev@hadoop.apache.org
Message-ID: <1607059079.1247160074825.JavaMail.jira@brutus>
Date: Thu, 9 Jul 2009 10:21:14 -0700 (PDT)
From: "stack (JIRA)" <jira@apache.org>
To: hbase-dev@hadoop.apache.org
Subject: [jira] Commented: (HBASE-1634) UI and shell list throw NPE
In-Reply-To: <2050514665.1247159955166.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

stack commented on HBASE-1634:
------------------------------

Here is sample NPE:

{code}
java.lang.NullPointerException
	at org.apache.hadoop.hbase.util.Writables.getWritable(Writables.java:74)
	at org.apache.hadoop.hbase.util.Writables.getHRegionInfo(Writables.java:118)
	at org.apache.hadoop.hbase.client.HConnectionManager$TableServers$1.processRow(HConnectionManager.java:355)
	at org.apache.hadoop.hbase.client.MetaScanner.metaScan(MetaScanner.java:63)
	at org.apache.hadoop.hbase.client.MetaScanner.metaScan(MetaScanner.java:28)
	at org.apache.hadoop.hbase.client.HConnectionManager$TableServers.listTables(HConnectionManager.java:369)
	at org.apache.hadoop.hbase.client.HBaseAdmin.listTables(HBaseAdmin.java:127)
..
{code}

This is not same as the old NPE we used to get in BaseScanner back in the day.

> UI and shell list throw NPE
> ---------------------------
>
>                 Key: HBASE-1634
>                 URL: https://issues.apache.org/jira/browse/HBASE-1634
>             Project: Hadoop HBase
>          Issue Type: Bug
>            Reporter: stack
>             Fix For: 0.20.0
>
>
> I have a .META. from bryan duxbury that has a row with only historian data.  List does whole row, not just info, so if only historian entries, a row is returned.  We then try and get a regioninfo from this row and NPE.
> As to why this happens, jd suggests that since we moved to async historian updates, row may have been deleted already.  Confirm.

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