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 "Hanisha Koneru (JIRA)" <ji...@apache.org> on 2017/08/25 22:29:00 UTC
[jira] [Updated] (HDFS-12358) Catch 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 ]
Hanisha Koneru updated HDFS-12358:
----------------------------------
Description:
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.
was: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). If this move fails, we need to catch it and delete the downloaded edit log from the tmp dir.
> Catch 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
>
> 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