[
https://issues.apache.org/jira/browse/HBASE-6443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13436564#comment-13436564
]
ramkrishna.s.vasudevan commented on HBASE-6443:
-----------------------------------------------
@Jon/Jimmy
This has got something to do with HDFS-3222? We had an internal patch for 0.90
version where we would try to get the blocklocations from NN based on retries.
If with in the retry i could find the block locations then the HLog will be non
emtpy. If not really it is an empty HLog File. This scenario happens in older
HDFS versions where the NN switches and internally if it was not able to get
the length 0 was getting returned without retrying.
I may be wrong here, but just thought it may be same. Thanks.
> HLogSplitter should ignore 0 length files
> -----------------------------------------
>
> Key: HBASE-6443
> URL: https://issues.apache.org/jira/browse/HBASE-6443
> Project: HBase
> Issue Type: Bug
> Reporter: Jimmy Xiang
> Assignee: Jimmy Xiang
> Fix For: 0.96.0, 0.94.1
>
>
> Somehow, some WAL files have size 0. Distributed log splitting can't handle
> it.
> HLogSplitter should ignore them.
--
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
