hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "dhruba borthakur (JIRA)" <j...@apache.org>
Subject [jira] Commented: (MAPREDUCE-1519) RaidNode fails to create new parity file if an older version already exists
Date Mon, 22 Feb 2010 05:48:28 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-1519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12836517#action_12836517
] 

dhruba borthakur commented on MAPREDUCE-1519:
---------------------------------------------

This is confusing me. A HDFS.rename() should succeed even if the target file exists. The rename
call deletes the original file and moves the new one to its place. Is this not what you are
seeing?

> RaidNode fails to create new parity file if an older version already exists
> ---------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-1519
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1519
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: contrib/raid
>            Reporter: Rodrigo Schmidt
>            Assignee: Rodrigo Schmidt
>         Attachments: MAPREDUCE-1519.patch
>
>
> When RaidNode tries to recreate a parity file for a source file that has been modified
(recreated) recently, it crashes.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message