hadoop-common-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: (HADOOP-6606) Change the default HADOOP_PID_DIR to $HADOOP_HOME/pids
Date Tue, 02 Mar 2010 17:13:27 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-6606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12840245#action_12840245
] 

Allen Wittenauer commented on HADOOP-6606:
------------------------------------------

I agree that having this as a config option is useful.  But the more and more I think about
this and the other jira's recently filed that much with hadoop-config.sh, the more convinced
I am that these changes are more harmful than helpful.  Instead of a one-time config option,
these changes basically do reconfig at *every* launch.  If we feel that users need a crutch
to properly configure their systems, it would be MUCH better to have a shell script that could
be run at install time that builds hadoop-env.sh for them.  Doing these config options at
runtime is going to be a performance killer, especially for interactive commands that get
used often like hadoop dfs..

> Change the default HADOOP_PID_DIR to $HADOOP_HOME/pids
> ------------------------------------------------------
>
>                 Key: HADOOP-6606
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6606
>             Project: Hadoop Common
>          Issue Type: Improvement
>    Affects Versions: 0.20.2
>            Reporter: Chad Metcalf
>            Assignee: Chad Metcalf
>         Attachments: HADOOP-6606.patch
>
>
> /tmp should not be used as a pid directory. There is too high a likelihood that pid files
could be altered or deleted. A more reasonable default is $HADOOP_HOME/pids. 

-- 
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