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

Jonathan Hsieh updated HBASE-7528:
----------------------------------

      Resolution: Fixed
    Hadoop Flags: Reviewed
          Status: Resolved  (was: Patch Available)
    
> Unhelpful NPE in hbck -repair when adopting orphans if no tableinfo is found.
> -----------------------------------------------------------------------------
>
>                 Key: HBASE-7528
>                 URL: https://issues.apache.org/jira/browse/HBASE-7528
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Jonathan Hsieh
>            Assignee: Sergey Shelukhin
>            Priority: Trivial
>         Attachments: HBASE-7528-v0.patch
>
>
> {code}
> 13/01/09 17:34:54 DEBUG util.HBaseFsck: Attempting to adopt orphan: { meta => 
> null, hdfs => 
> hdfs://c1514.hal.cloudera.com:56020/hbase-cdh4.2/pe-2-table/28fbe62eee2ffd8ea2611335ed78f8ce,
>  deployed =>  }
> Exception in thread "main" java.lang.NullPointerException
>         at 
> org.apache.hadoop.hbase.util.HBaseFsck$TableInfo.access$000(HBaseFsck.java:1871)
>         at 
> org.apache.hadoop.hbase.util.HBaseFsck.adoptHdfsOrphan(HBaseFsck.java:482)
>         at 
> org.apache.hadoop.hbase.util.HBaseFsck.adoptHdfsOrphans(HBaseFsck.java:455)
>         at 
> org.apache.hadoop.hbase.util.HBaseFsck.restoreHdfsIntegrity(HBaseFsck.java:576)
>         at 
> org.apache.hadoop.hbase.util.HBaseFsck.offlineHdfsIntegrityRepair(HBaseFsck.java:353)
>         at 
> org.apache.hadoop.hbase.util.HBaseFsck.onlineHbck(HBaseFsck.java:431)
>         at org.apache.hadoop.hbase.util.HBaseFsck.exec(HBaseFsck.java:3614)
>         at org.apache.hadoop.hbase.util.HBaseFsck.run(HBaseFsck.java:3436)
>         at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70)
>         at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:84)
>         at org.apache.hadoop.hbase.util.HBaseFsck.main(HBaseFsck.java:3430)
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to