Return-Path: X-Original-To: apmail-hadoop-user-archive@minotaur.apache.org Delivered-To: apmail-hadoop-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 12FD2E57E for ; Thu, 28 Feb 2013 09:35:13 +0000 (UTC) Received: (qmail 24231 invoked by uid 500); 28 Feb 2013 09:35:08 -0000 Delivered-To: apmail-hadoop-user-archive@hadoop.apache.org Received: (qmail 23838 invoked by uid 500); 28 Feb 2013 09:35:07 -0000 Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hadoop.apache.org Delivered-To: mailing list user@hadoop.apache.org Received: (qmail 23810 invoked by uid 99); 28 Feb 2013 09:35:06 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 Feb 2013 09:35:06 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of azuryyyu@gmail.com designates 209.85.210.176 as permitted sender) Received: from [209.85.210.176] (HELO mail-ia0-f176.google.com) (209.85.210.176) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 Feb 2013 09:35:01 +0000 Received: by mail-ia0-f176.google.com with SMTP id i18so1325185iac.35 for ; Thu, 28 Feb 2013 01:34:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=jcAZfcqQsBhJ2PfxX3Yn83gPzb/9Umg+bxCxWtQGX/I=; b=fkpNVqPXaz32OUYZ07sR6GXCNajpbI/0df9sHJzTxK4cno8F9KMRJBU9hagLjOPmtC n8PbevkVYFq7z5Brz7cLvH5Ax3+XCvJVdE5ktUzd0tYi9gObuQvKW7ptakTO0yQCsWSB 2BBf5/H0xMe1iLurNHZ2sq79XsAOFlGu2ki7GA2BbugYT7gP8it4skI4Sq+ptkMmAEFG zKIzBjrWVuqHXvRtHMmfU3AiVZjyv1g2L5yAO7GSnhCIyqmTVbEmWEsGjLcJ0HOlM4Nr JgjGERh4Hp4GKTdzyJpV9SW9Lip82SARuAzPMHJ+PBFejId/aT0ypZGQ8Ak1v9D8NYKv vdMg== MIME-Version: 1.0 X-Received: by 10.43.135.68 with SMTP id if4mr2716508icc.44.1362044081216; Thu, 28 Feb 2013 01:34:41 -0800 (PST) Received: by 10.64.26.70 with HTTP; Thu, 28 Feb 2013 01:34:41 -0800 (PST) In-Reply-To: References: Date: Thu, 28 Feb 2013 17:34:41 +0800 Message-ID: Subject: Fwd: [jira] [Commented] (HDFS-4533) start-dfs.sh ignored additional parameters besides -upgrade From: Azuryy Yu To: user@hadoop.apache.org Content-Type: multipart/alternative; boundary=20cf307f35fca1343e04d6c59923 X-Virus-Checked: Checked by ClamAV on apache.org --20cf307f35fca1343e04d6c59923 Content-Type: text/plain; charset=ISO-8859-1 Who can review this JIRA(https://issues.apache.org/jira/browse/HDFS-4533), which is very simple. ---------- Forwarded message ---------- From: Hadoop QA (JIRA) Date: Wed, Feb 27, 2013 at 4:53 PM Subject: [jira] [Commented] (HDFS-4533) start-dfs.sh ignored additional parameters besides -upgrade To: azuryyyu@gmail.com [ https://issues.apache.org/jira/browse/HDFS-4533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13588130#comment-13588130] Hadoop QA commented on HDFS-4533: --------------------------------- {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12571164/HDFS-4533.patch against trunk revision . {color:red}-1 patch{color}. The patch command could not apply the patch. Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/4008//console This message is automatically generated. > start-dfs.sh ignored additional parameters besides -upgrade > ----------------------------------------------------------- > > Key: HDFS-4533 > URL: https://issues.apache.org/jira/browse/HDFS-4533 > Project: Hadoop HDFS > Issue Type: Bug > Components: datanode, namenode > Affects Versions: 2.0.3-alpha > Reporter: Fengdong Yu > Labels: patch > Fix For: 2.0.4-beta > > Attachments: HDFS-4533.patch > > > start-dfs.sh only takes -upgrade option and ignored others. > So If run the following command, it will ignore the clusterId option. > start-dfs.sh -upgrade -clusterId 1234 -- 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 --20cf307f35fca1343e04d6c59923 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Who can review this JIRA(https:= //issues.apache.org/jira/browse/HDFS-4533), which is very simple.

---------- Forwarded message ----------
F= rom: Hadoop QA (JIRA) &= lt;jira@apache.org>
Dat= e: Wed, Feb 27, 2013 at 4:53 PM
Subject: [jira] [Commented] (HDFS-4533) start-dfs.sh ignored additional par= ameters besides -upgrade
To: azury= yyu@gmail.com



=A0 =A0 [ https://issues= .apache.org/jira/browse/HDFS-4533?page=3Dcom.atlassian.jira.plugin.system.i= ssuetabpanels:comment-tabpanel&focusedCommentId=3D13588130#comment-1358= 8130 ]

Hadoop QA commented on HDFS-4533:
---------------------------------

{color:red}-1 overall{color}. =A0Here are the results of testing the latest= attachment
=A0 http://issues.apache.org/jira/secure/attach= ment/12571164/HDFS-4533.patch
=A0 against trunk revision .

=A0 =A0 {color:red}-1 patch{color}. =A0The patch command could not apply th= e patch.

Console output: https://builds.apache.org/job/PreCommit= -HDFS-Build/4008//console

This message is automatically generated.

> start-dfs.sh ignored additional parameters besides -upgrade
> -----------------------------------------------------------
>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Key: HDFS-4533
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 URL: https://issues.apache.org/jira= /browse/HDFS-4533
> =A0 =A0 =A0 =A0 =A0 =A0 Project: Hadoop HDFS
> =A0 =A0 =A0 =A0 =A0Issue Type: Bug
> =A0 =A0 =A0 =A0 =A0Components: datanode, namenode
> =A0 =A0Affects Versions: 2.0.3-alpha
> =A0 =A0 =A0 =A0 =A0 =A0Reporter: Fengdong Yu
> =A0 =A0 =A0 =A0 =A0 =A0 =A0Labels: patch
> =A0 =A0 =A0 =A0 =A0 =A0 Fix For: 2.0.4-beta
>
> =A0 =A0 =A0 =A0 Attachments: HDFS-4533.patch
>
>
> start-dfs.sh only takes -upgrade option and ignored others.
> So If run the following command, it will ignore the clusterId option.<= br> > start-dfs.sh -upgrade -clusterId 1234

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrato= rs
For more information on JIRA, see: http://www.atlassian.com/software/jira

--20cf307f35fca1343e04d6c59923--