You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-issues@hadoop.apache.org by "Gaurav Kanade (JIRA)" <ji...@apache.org> on 2015/10/16 02:09:05 UTC

[jira] [Commented] (HADOOP-12484) Single File Rename Throws Incorrectly In Potential Race Condition Scenarios

    [ https://issues.apache.org/jira/browse/HADOOP-12484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14959898#comment-14959898 ] 

Gaurav Kanade commented on HADOOP-12484:
----------------------------------------

[~onpduo], [~linchan], [~dchickabasapa], [~cnauroth], [~pravinmittal] [~fengs] [~enis] [~sjiang] - could you please review this patch soon ? This is important to unblock further testing of HBASE-246 in HDP 2.3 certification tests (https://hwxmonarch.atlassian.net/browse/HBASE-246)

> Single File Rename Throws Incorrectly In Potential Race Condition Scenarios
> ---------------------------------------------------------------------------
>
>                 Key: HADOOP-12484
>                 URL: https://issues.apache.org/jira/browse/HADOOP-12484
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: tools
>            Reporter: Gaurav Kanade
>            Assignee: Gaurav Kanade
>         Attachments: HADOOP-12484.01.patch
>
>
> FinishSingleFileRename function - in the case where src and dst both exist gets a lease on src blob to block write access and then deletes the file. However in the time between checking existence of source file and acquiring lease the file may be deleted by another process (race condition). Presently the function simply throws in this scenario. In this case the function should treat this as a case where rename is complete; i.e. catch the exception and if this is the cause exit gracefully with the result that the rename is complete



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)