hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] Created: (HBASE-766) FileNotFoundException trying to load HStoreFile 'data'
Date Wed, 23 Jul 2008 18:02:31 GMT
FileNotFoundException trying to load HStoreFile 'data'

                 Key: HBASE-766
                 URL: https://issues.apache.org/jira/browse/HBASE-766
             Project: Hadoop HBase
          Issue Type: Bug
            Reporter: stack
            Priority: Critical
             Fix For: 0.2.0

>From Renaud Delbru up on the list:

after our issues ("Replay of HLog required", in a precious thread) with HBase, it seems that
HBase has corrupted regions.
We have, on the three region servers, errors stating that HBase cannot open certain regions
because some map files on hdfs are missing (see the log attached).

Do you have any ideas how to fix this ?


java.io.FileNotFoundException: File does not exist: hdfs://hadoop1.sindice.net:54310/hbase/page-repository/1105668475/field/mapfiles/5122893264992435570/data
  at org.apache.hadoop.dfs.DistributedFileSystem.getFileStatus(DistributedFileSystem.java:369)
  at org.apache.hadoop.hbase.regionserver.HStoreFile.length(HStoreFile.java:464)
  at org.apache.hadoop.hbase.regionserver.HStore.loadHStoreFiles(HStore.java:409)
  at org.apache.hadoop.hbase.regionserver.HStore.<init>(HStore.java:236)
  at org.apache.hadoop.hbase.regionserver.HRegion.instantiateHStore(HRegion.java:1575)
  at org.apache.hadoop.hbase.regionserver.HRegion.<init>(HRegion.java:451)
  at org.apache.hadoop.hbase.regionserver.HRegionServer.instantiateRegion(HRegionServer.java:901)
  at org.apache.hadoop.hbase.regionserver.HRegionServer.openRegion(HRegionServer.java:876)
  at org.apache.hadoop.hbase.regionserver.HRegionServer$Worker.run(HRegionServer.java:816)
  at java.lang.Thread.run(Thread.java:619)


I'd thought we'd added handling of this kind of event post HDFS crashings but looking in code,
it seems that TRUNK may not have been fixed up properly.

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

View raw message