[
https://issues.apache.org/jira/browse/HADOOP-9253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arpit Gupta updated HADOOP-9253:
--------------------------------
Attachment: HADOOP-9253.branch-1.patch
@Harsh
I have updated the patch to handle a secure datanode startup. I tested on a
secure and un secure cluster and the appropriate info was captured. Let me know
if the approach looks good and i will provide a similar patch for trunk.
@Andy
I am not quite sure i understand what you are referring to. The log file that
is being printed to the console should never have any left over contents as
start commands overwrites it.
{code}
nohup nice -n $HADOOP_NICENESS "$HADOOP_PREFIX"/bin/hadoop --config
$HADOOP_CONF_DIR $command "$@" > "$log" 2>&1 < /dev/null &
{code}
But if you think the problem still exists can open another jira for it.
> Capture ulimit info in the logs at service start time
> -----------------------------------------------------
>
> Key: HADOOP-9253
> URL: https://issues.apache.org/jira/browse/HADOOP-9253
> Project: Hadoop Common
> Issue Type: Improvement
> Affects Versions: 1.1.1, 2.0.2-alpha
> Reporter: Arpit Gupta
> Assignee: Arpit Gupta
> Attachments: HADOOP-9253.branch-1.patch, HADOOP-9253.branch-1.patch,
> HADOOP-9253.patch
>
>
> output of ulimit -a is helpful while debugging issues on the system.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
