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] [Updated] (MAPREDUCE-496) If mapred.local.dir is configured on top of dfs.data.dir, hadoop should refuse to start rather than deleting the contents of local.dir
Date Mon, 21 Jul 2014 17:04:39 GMT

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

Allen Wittenauer updated MAPREDUCE-496:
---------------------------------------

    Labels: newbie  (was: )

> If mapred.local.dir is configured on top of dfs.data.dir, hadoop should refuse to start
rather than deleting the contents of local.dir
> --------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-496
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-496
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>            Reporter: Todd Lipcon
>            Priority: Minor
>              Labels: newbie
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> I just managed to blow away a DFS by accidentally misconfiguring dfs.data.dir and mapred.local.dir
to contain several directories in common. On startup, the task tracker clears out mapred.local.dir,
which obviously screws over the datanode.
> This should be a reasonably easy check to put in place to make hadoop more idiot proof
(or in my case lack-of-sleep proof)



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message