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

Posted to hdfs-issues@hadoop.apache.org by "Arpit Agarwal (JIRA)" <ji...@apache.org> on 2017/08/27 05:50:00 UTC

[jira] [Updated] (HDFS-12358) Handle IOException when transferring edit log to Journal current dir through JN sync

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

Arpit Agarwal updated HDFS-12358:
---------------------------------
       Resolution: Fixed
     Hadoop Flags: Reviewed
    Fix Version/s: 3.0.0-beta1
           Status: Resolved  (was: Patch Available)

I've committed this. The test failures are unrelated.

Thanks for the contribution [~hanishakoneru].

> Handle IOException when transferring edit log to Journal current dir through JN sync
> ------------------------------------------------------------------------------------
>
>                 Key: HDFS-12358
>                 URL: https://issues.apache.org/jira/browse/HDFS-12358
>             Project: Hadoop HDFS
>          Issue Type: Bug
>            Reporter: Hanisha Koneru
>            Assignee: Hanisha Koneru
>             Fix For: 3.0.0-beta1
>
>         Attachments: HDFS-12358.001.patch, HDFS-12358.002.patch, HDFS-12358.003.patch
>
>
> During JN sync, a missing edit log is first downloaded from a remote JN to a tmp dir and then moved to the current directory (protected by the Journal's synchronization). 
> Irrespective of whether the move succeeds or fails, we should delete the tmp file.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org