hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Allen Wittenauer (JIRA)" <j...@apache.org>
Subject [jira] Commented: (MAPREDUCE-2181) mapreduce.jobtracker.staging.root.dir default is unreasonable
Date Wed, 10 Nov 2010 01:19:14 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-2181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12930403#action_12930403

Allen Wittenauer commented on MAPREDUCE-2181:

I'm not a fan of /user.  I can see major problems with sites that set quotas.

Why not just make it an explicit /tmp?

[FWIW, I use /system to keep it completely separate from everything.]

> mapreduce.jobtracker.staging.root.dir default is unreasonable
> -------------------------------------------------------------
>                 Key: MAPREDUCE-2181
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2181
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: job submission, jobtracker
>    Affects Versions: 0.22.0
>            Reporter: Todd Lipcon
> The default for mapreduce.jobtracker.staging.root.dir is set to ${hadoop.tmp.dir}/mapred/staging,
which doesn't really work on a normal cluster. hadoop.tmp.dir is overloaded in different places
where sometimes it is a local path and sometimes it is a path on HDFS, which makes things
even more confusing.
> We should change the default for the staging directory to /user (as is suggested by the
description of that configuration) and then fix LocalJobRunner to use a different configuration
-- perhaps mapreduce.localjobrunner.staging.root.dir -- to make it clear that it's a *local*
path. That one could legitimately default to something inside hadoop.tmp.dir.

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

View raw message