hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Enis Soztutar (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-8314) HLogSplitter can retry to open a 0-length hlog file
Date Fri, 03 May 2013 02:12:15 GMT

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

Enis Soztutar commented on HBASE-8314:

Thanks Jimmy, I failed to see that in the patch. 
bq. However, according to HBASE-8389, HBASE-7878 may not always work.
That is not my takeaway from N's comments here: https://issues.apache.org/jira/browse/HBASE-8389?focusedCommentId=13642669&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13642669
> HLogSplitter can retry to open a 0-length hlog file
> ---------------------------------------------------
>                 Key: HBASE-8314
>                 URL: https://issues.apache.org/jira/browse/HBASE-8314
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Jimmy Xiang
>            Assignee: Jimmy Xiang
>             Fix For: 0.98.0, 0.95.1
>         Attachments: region-server.log, trunk-8314.patch, trunk-8314_v2.patch
> In case a HLog file is of size 0, and it is under recovery, HLogSplitter will fail to
open it since it can get the file length, therefore, master can't start.
> {noformat}
> java.io.IOException: Cannot obtain block length for LocatedBlock{...; getBlockSize()=0;
corrupt=false; offset=0; locs=[...]}
>     at org.apache.hadoop.hdfs.DFSInputStream.readBlockLength(DFSInputStream.java:238)
>     at org.apache.hadoop.hdfs.DFSInputStream.fetchLocatedBlocksAndGetLastBlockLength(DFSInputStream.java:182)
>     at org.apache.hadoop.hdfs.DFSInputStream.openInfo(DFSInputStream.java:124)
>     at org.apache.hadoop.hdfs.DFSInputStream.<init>(DFSInputStream.java:117)
>     at org.apache.hadoop.hdfs.DFSClient.open(DFSClient.java:1080)
> {noformat}

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

View raw message