[
https://issues.apache.org/jira/browse/HADOOP-6391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12790667#action_12790667
]
Hudson commented on HADOOP-6391:
--------------------------------
Integrated in Hadoop-Common-trunk #188 (See
[http://hudson.zones.apache.org/hudson/job/Hadoop-Common-trunk/188/])
. Classpath should not be part of command line arguments. Contributed by
Cristian Ivascu.
> Classpath should not be part of command line arguments
> ------------------------------------------------------
>
> Key: HADOOP-6391
> URL: https://issues.apache.org/jira/browse/HADOOP-6391
> Project: Hadoop Common
> Issue Type: Bug
> Components: scripts
> Affects Versions: 0.21.0, 0.22.0
> Reporter: Cristian Ivascu
> Assignee: Cristian Ivascu
> Fix For: 0.22.0
>
> Attachments: HADOOP-6391.patch
>
>
> Because bin/hadoop and bin/hdfs put the entire CLASSPATH in the command line
> arguments, it exceeds 4096 bytes, which is the maximum size that ps (or
> /proc) can work with. This makes looking for the processes difficult, since
> the output gets truncated for all components at the same point (e.g.
> NameNode, SecondaryNameNode, DataNode).
> The mapred sub-project does not have this problem, because it calls "export
> CLASSPATH" before the final exec. bin/hadoop and bin/hdfs should do the same
> thing
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
