Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hbase-dev@hadoop.apache.org
Message-ID: <347279960.1217545351700.JavaMail.jira@brutus>
Date: Thu, 31 Jul 2008 16:02:31 -0700 (PDT)
From: "stack (JIRA)" <jira@apache.org>
To: hbase-dev@hadoop.apache.org
Subject: [jira] Resolved: (HBASE-766) FileNotFoundException trying to load
 HStoreFile 'data'
In-Reply-To: <1618874412.1216836151674.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-766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stack resolved HBASE-766.
-------------------------

    Resolution: Fixed

Resolving. JGray says it works.

Looks like I committed this fix already as part of another patch:

------------------------------------------------------------------------
r680910 | stack | 2008-07-29 21:37:06 -0700 (Tue, 29 Jul 2008) | 1 line

HBASE-783 For single row, single family retrieval, getRow() works half as fast as getScanner().next()


> 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
>            Assignee: stack
>            Priority: Critical
>             Fix For: 0.2.0
>
>         Attachments: 766.patch, hs.patch
>
>
> From Renaud Delbru up on the list:
> {code}
> Hi,
> 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 ?
> Thanks.
> 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)
> {code}
> 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.