[
https://issues.apache.org/jira/browse/HBASE-6649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13454347#comment-13454347
]
Devaraj Das commented on HBASE-6649:
------------------------------------
This log file belongs to a crashed RS, and yes, it seems like the last record
wasn't completely written to the file before the RS crashed. That should be
fine, i.e., no dataloss should happen - in the queueFailover test, the client
would have got exceptions to the flushCommit call and it would have retried the
batch of 'put' and the corresponding records would have ended up in another RS.
> [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
