You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-issues@hadoop.apache.org by "Cristian Ivascu (JIRA)" <ji...@apache.org> on 2009/11/25 17:13:39 UTC

[jira] Updated: (HADOOP-6391) Classpath should not be part of command line arguments

     [ https://issues.apache.org/jira/browse/HADOOP-6391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Cristian Ivascu updated HADOOP-6391:
------------------------------------

        Fix Version/s: 0.22.0
                       0.21.0
    Affects Version/s: 0.22.0
                       0.21.0
               Status: Patch Available  (was: Open)

no tests are included because there is no framework to test for changes in the hadoop starting scripts.

> 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
>             Fix For: 0.21.0, 0.22.0
>
>
> 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.