Mailing-List: contact common-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-dev@hadoop.apache.org
Message-ID: <1368215263.1259157759585.JavaMail.jira@brutus>
Date: Wed, 25 Nov 2009 14:02:39 +0000 (UTC)
From: "Cristian Ivascu (JIRA)" <jira@apache.org>
To: common-dev@hadoop.apache.org
Subject: [jira] Created: (HADOOP-6391) Classpath should not be part of
 command line arguments
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

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
            Reporter: Cristian Ivascu


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.