Please find the logs in HRegionServer. Did you mean this Ted?
2012-02-18 00:44:38,808 INFO org.apache.hadoop.hbase.util.FSUtils: Finished
lease recover attempt for
2012-02-18 00:44:38,808 WARN
20.1329492399793 might be still open, length is 0
2012-02-18 00:44:38,811 WARN
org.apache.hadoop.hbase.regionserver.wal.HLogSplitter: Could not open
20.1329492399793 for reading. File is emptyjava.io.EOFException
Sent: Tuesday, February 21, 2012 8:39 PM
Cc: firstname.lastname@example.org; rama krishna
Subject: Re: Handling EOFexception while splitlog
Can you provide stack trace for this issue ?
On Feb 21, 2012, at 8:52 AM, "Ramkrishna.S.Vasudevan"
We ran into one issue while splitting HLogs due to EOFException. (0.90.6
Due to some reason the DNs were not able to connect to NN (network
fluctuation) and the master was splitting the logs.
While parsing the hlog, we get the length and we expect it might be 0. (No
But in this scenario the DFSClient throws an EOFException as all DNs are not
able to connect to NN and due to that the while reading we get an
In this specific case we just return and the master considers the split to
be successful. This leads to data loss.
May be this can be fixed from HDFS side, I would like to know can we throw
an IOException in this case and make the split log to be retried as we have
a retry logic now.
I was going through HBASE-2643 as part of which EOFException was handled and
dint find this scenario in that.
Please provide your suggestions.