[ 
https://issues.apache.org/jira/browse/HADOOP-14434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chris Douglas reassigned HADOOP-14434:
--------------------------------------

             Assignee:     (was: Lukas Majercak)
    Affects Version/s:     (was: 3.0.0-alpha2)
                           (was: 3.0.0-alpha1)
                           (was: 2.7.3)
                           (was: 2.7.1)
                       2.7.1
                       2.7.3
                       3.0.0-alpha1
                       3.0.0-alpha2
          Component/s:     (was: hdfs)
                           (was: native)
                           (was: rolling upgrades)
                       native
                  Key: HADOOP-14434  (was: HDFS-11713)
              Project: Hadoop Common  (was: Hadoop HDFS)

> Use MoveFileEx to allow renaming a file when the destination exists
> -------------------------------------------------------------------
>
>                 Key: HADOOP-14434
>                 URL: https://issues.apache.org/jira/browse/HADOOP-14434
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: native
>    Affects Versions: 3.0.0-alpha2, 3.0.0-alpha1, 2.7.3, 2.7.1
>            Reporter: Lukas Majercak
>              Labels: windows
>         Attachments: HDFS-11713.001.patch
>
>
> The {{NativeIO.c#renameTo0}} currently uses {{MoveFile}} Windows system call, 
> which fails when renaming a file to a destination that already exists.
> This makes the {{TestRollingUpgrade.testRollback}} test fail on Windows, as 
> during that execution, a DataNode tries to rename block's meta file to a 
> destination that exists.
> The proposal is to change to using {{MoveFileEx}} Windows call, and passing 
> in {{MOVEFILE_REPLACE_EXISTING}} flag to force the renaming.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to