hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Raghu Angadi (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-1875) multiple dfs.client.buffer.dir directories are not treated as alternatives
Date Tue, 11 Sep 2007 18:47:32 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-1875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12526555

Raghu Angadi commented on HADOOP-1875:

DFS client uses {{LocalDirAllocator.createTmpFileWrite()}}

{{LocalDirAllocator}} explicitly states that it does not check for write permissions. I think
it should try different directory when create on one dir fails (for whatever reason).

Also during initialization it ignores the error while trying to {{mkdirs(dir[i])}}.

> multiple dfs.client.buffer.dir directories are not treated as alternatives
> --------------------------------------------------------------------------
>                 Key: HADOOP-1875
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1875
>             Project: Hadoop
>          Issue Type: Bug
>          Components: mapred
>            Reporter: Christian Kunz
>             Fix For: 0.15.0
> When specifying multiple directories in the value for dfs.client.buffer.dir, jobs fail
when the selected directory does not exist or is not writable. Correct behaviour should be
to create the directory when it does not exist and fail over to an alternative directory when
it is not writable.

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

View raw message