Return-Path: X-Original-To: apmail-hadoop-mapreduce-user-archive@minotaur.apache.org Delivered-To: apmail-hadoop-mapreduce-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 2C17AE472 for ; Sat, 9 Mar 2013 00:06:05 +0000 (UTC) Received: (qmail 55711 invoked by uid 500); 9 Mar 2013 00:06:00 -0000 Delivered-To: apmail-hadoop-mapreduce-user-archive@hadoop.apache.org Received: (qmail 55625 invoked by uid 500); 9 Mar 2013 00:05:59 -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 55617 invoked by uid 99); 9 Mar 2013 00:05:59 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 09 Mar 2013 00:05:59 +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 (nike.apache.org: domain of suresh@hortonworks.com designates 209.85.216.52 as permitted sender) Received: from [209.85.216.52] (HELO mail-qa0-f52.google.com) (209.85.216.52) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 09 Mar 2013 00:05:54 +0000 Received: by mail-qa0-f52.google.com with SMTP id bs12so90381qab.18 for ; Fri, 08 Mar 2013 16:05:33 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type:x-gm-message-state; bh=Rw1YJwSIoLkIjU9D88rVDKFOXdHEay6z6G0AFNxX5eg=; b=NgWIr6nWB6bzRhzwW8eJgshbqGNybVIzpvxFd9wlykeRTJFfGEcSVYK5oZnHCKmZvp QgurAofEpy/5rgNOpjII2ng5I47a64B5UiOGHXmeXZS/RHOQqmjW7I960m0hNYgO26Ie m7FBoM07Ig9fcPhvynl2S7KClKDJK6OPHWd3IdsdnHH9l0CVSE6SFReAZpD6nS/0R//c 2Fv/qdy030XuSoVFBsSZbdx+/+Wie1IA0vQ4BLrAbYguYpW98Pp4bxRDUnc5b46o6mOa NTB5MNn2NHEDt/rlbU6VE0j3YSmWtuJV2lJT2aMu2UwqtehZD8JZC44oyATzk7Y5zKbY I6tA== MIME-Version: 1.0 X-Received: by 10.224.185.198 with SMTP id cp6mr6659877qab.59.1362787533357; Fri, 08 Mar 2013 16:05:33 -0800 (PST) Received: by 10.49.29.166 with HTTP; Fri, 8 Mar 2013 16:05:33 -0800 (PST) In-Reply-To: References: Date: Fri, 8 Mar 2013 16:05:33 -0800 Message-ID: Subject: Re: [jira] [Commented] (HDFS-4533) start-dfs.sh ignored additional parameters besides -upgrade From: Suresh Srinivas To: "hdfs-user@hadoop.apache.org" Content-Type: multipart/alternative; boundary=485b397dd677d48ab504d772b2cc X-Gm-Message-State: ALoCoQmAsw7Fs0pOy7nZIHiQ23ODhhRpqB+fRQHX7McXGXvjCt+FjHd6BEeX3LfGVEoqUn5HQeD7 X-Virus-Checked: Checked by ClamAV on apache.org --485b397dd677d48ab504d772b2cc Content-Type: text/plain; charset=ISO-8859-1 Please followup on Jenkins failures. Looks like the patch is generated at the wrong directory. On Thu, Feb 28, 2013 at 1:34 AM, Azuryy Yu wrote: > 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 > > -- http://hortonworks.com/download/ --485b397dd677d48ab504d772b2cc Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Please followup on Jenkins failures. Looks like the patch = is generated at the wrong directory.

On Thu, Feb 28, 2013 at 1:34 AM, Azuryy Yu <= azuryyyu@gmail.com> wrote:
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= >
Date: Wed, Feb 27, 2013 at 4:53 PM
Subject: [jira] [Commented] (HDFS-4533) start-dfs.sh ignored additional par= ameters besides -upgrade
To: azuryyyu@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




--
http://h= ortonworks.com/download/
--485b397dd677d48ab504d772b2cc--