[
https://issues.apache.org/jira/browse/HBASE-6649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13458185#comment-13458185
]
Jean-Daniel Cryans commented on HBASE-6649:
-------------------------------------------
[~devaraj] I'm still trying to figure out exactly how we get the
IndexOutOfBoundsException (I'd say the file didn't get new data and we started
reading exactly at the end and the DFSClient doesn't like that? Or it's missing
something at the end?), but if it's a case of reading the tail of a recovered
log then we *could* add a check like this:
{code}
try {
entry = this.reader.next(entriesArray[currentNbEntries]);
} catch (IOException ie) {
if (queueRecovered) {
LOG.debug("Break on IOE: " + ie.getMessage());
break;
} else {
throw ie;
}
}
{code}
> [0.92 UNIT TESTS] TestReplication.queueFailover occasionally fails [Part-1]
> ---------------------------------------------------------------------------
>
> Key: HBASE-6649
> URL: https://issues.apache.org/jira/browse/HBASE-6649
> Project: HBase
> Issue Type: Bug
> Reporter: Devaraj Das
> Assignee: Devaraj Das
> Fix For: 0.96.0, 0.92.3, 0.94.2
>
> Attachments: 6649-0.92.patch, 6649-1.patch, 6649-2.txt,
> 6649-trunk.patch, 6649-trunk.patch, 6649.txt, HBase-0.92 #495 test -
> queueFailover [Jenkins].html, HBase-0.92 #502 test - queueFailover
> [Jenkins].html
>
>
> Have seen it twice in the recent past: http://bit.ly/MPCykB &
> http://bit.ly/O79Dq7 ..
> Looking briefly at the logs hints at a pattern - in both the failed test
> instances, there was an RS crash while the test was running.
--
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
