hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lipcon (JIRA)" <j...@apache.org>
Subject [jira] Created: (HADOOP-4800) 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 Sat, 06 Dec 2008 22:39:44 GMT
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: HADOOP-4800
                 URL: https://issues.apache.org/jira/browse/HADOOP-4800
             Project: Hadoop Core
          Issue Type: Improvement
          Components: mapred
    Affects Versions: 0.19.0
            Reporter: Todd Lipcon
            Priority: Minor


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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message