Description
The following configuration causes problems:
<property>
<name>dfs.data.dir</name>
<value>/mnt/hstore2/hdfs, /home/foo/dfs</value>
<description>
Determines where on the local filesystem an DFS data node should store its bl
ocks. If this is a comma-delimited list of directories, then data will be stor
ed in all named directories, typically on different devices. Directories that
do not exist are ignored.
</description>
</property>
The problem is that the space after the comma causes the second directory for storage to be " /home/foo/dfs" which is in a directory named <SPACE> which contains a sub-dir named "home" in the hadoop datanodes default directory. This will typically cause the user's home partition to fill, but will be very hard for the user to understand since a directory with a whitespace name is hard to understand.
My proposed solution would be to trimLeft all path names from this and similar property after splitting on comma. This still allows spaces in file and directory names but avoids this problem.
Attachments
Attachments
Issue Links
- is depended upon by
-
HDFS-455 Make NN and DN handle in a intuitive way comma-separated configuration strings
- Resolved
- is part of
-
HADOOP-3582 Improve how Hadoop gets configured
- Open
- relates to
-
HADOOP-4212 New lines and leading spaces are not trimmed of a value when configuration is read
- Resolved
-
MAPREDUCE-1441 Configuration of directory lists should trim whitespace
- Resolved