Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 10 Aug 2012 02:24:31 +0000 (UTC)
From: "liuli (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <267360266.93.1344565471297.JavaMail.jiratomcat@issues-vm>
In-Reply-To: 
 <1958269903.22931.1336068531352.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HBASE-5928) Hbck shouldn't npe when there are
 no tables.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

liuli commented on HBASE-5928:
------------------------------

Hi Jonathan. Now the environment is being used by others. I will keep in mind, and when I could, I will double check what you said
Yes, I opened a new issue HBASE-6500, if you need, I could close that one and only trace the status here

Anyway, I will keep you posted!
                
> Hbck shouldn't npe when there are no tables.
> --------------------------------------------
>
>                 Key: HBASE-5928
>                 URL: https://issues.apache.org/jira/browse/HBASE-5928
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 0.92.1, 0.94.0, 0.96.0
>            Reporter: Elliott Clark
>            Assignee: Elliott Clark
>            Priority: Minor
>             Fix For: 0.92.2, 0.96.0, 0.94.1
>
>         Attachments: HBASE-5928-0.patch, HBASE-5928-1.patch, hbase-5928-94.patch
>
>
> hbase fsck errors out when there are no tables.
> Exception in thread "main" java.lang.NullPointerException
> 	at org.apache.hadoop.hbase.util.HBaseFsck.reportTablesInFlux(HBaseFsck.java:560)
> 	at org.apache.hadoop.hbase.util.HBaseFsck.onlineConsistencyRepair(HBaseFsck.java:346)
> 	at org.apache.hadoop.hbase.util.HBaseFsck.onlineHbck(HBaseFsck.java:382)
> 	at org.apache.hadoop.hbase.util.HBaseFsck.main(HBaseFsck.java:3120)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira