hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lipcon (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-2929) HA: stress test and fixes for block synchronization
Date Fri, 17 Feb 2012 01:25:59 GMT

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

Todd Lipcon commented on HDFS-2929:

Looping the test for a while I got it to fail, saw the following in the logs:

java.io.IOException: THIS IS NOT SUPPOSED TO HAPPEN: replica.getGenerationStamp() >= recoveryId
= 2349, block=blk_6372807635021754619_1978, replica=FinalizedReplica, blk_6372807635021754619_2349,

So need to keep looking into this. I also want to run the same test in a non-HA scenario to
see if this is an existing trunk bug. If it is, it should not block HA.
> HA: stress test and fixes for block synchronization
> ---------------------------------------------------
>                 Key: HDFS-2929
>                 URL: https://issues.apache.org/jira/browse/HDFS-2929
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: ha, name-node
>    Affects Versions: HA branch (HDFS-1623)
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>            Priority: Critical
>         Attachments: hdfs-2929.txt, hdfs-2929.txt
> We have a couple of TODOs in {{commitBlockSynchronization}} and {{syncBlock}} around
HA. I think the current behavior may in fact be correct, but I plan to write a stress test
/ functional test for better coverage of this area.

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


View raw message