Return-Path: X-Original-To: apmail-hadoop-hdfs-user-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-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 6B636E4BB for ; Wed, 27 Feb 2013 08:45:22 +0000 (UTC) Received: (qmail 17287 invoked by uid 500); 27 Feb 2013 08:45:17 -0000 Delivered-To: apmail-hadoop-hdfs-user-archive@hadoop.apache.org Received: (qmail 17059 invoked by uid 500); 27 Feb 2013 08:45:16 -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 17003 invoked by uid 99); 27 Feb 2013 08:45:15 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 Feb 2013 08:45:15 +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 azuryyyu@gmail.com designates 209.85.210.178 as permitted sender) Received: from [209.85.210.178] (HELO mail-ia0-f178.google.com) (209.85.210.178) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 Feb 2013 08:45:03 +0000 Received: by mail-ia0-f178.google.com with SMTP id y26so250363iab.23 for ; Wed, 27 Feb 2013 00:44:43 -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=1xZ+49Y8JMRzvyOQWqyUJaK44HRwqWwYkGctz4JZUrI=; b=HYo6e4xR7hXyhxeHiWuEbQ/oRw9UgJ9m6kKv5A9iibYFWM/bQ+yvUUxLp753K0y98M 4vBczrLDyXNJtBa4K9aJ6cHmj3k0GYztEDRrNEp0BS3ZIXYLQ3cfdWGEXaoWvSI9NRru RJJ0Fy91ahedgWaBbLgCqr7qfZDLUuNwSqSntKW67AYf2jDQ9UW/5Gn70FAGcrtz8clJ ekk0OZILpruDqCks4I1mzZLmw2N13fqFKOQHdWaMz32oc+6A0Dr0AMLrcpyaFHsX7mEt R7AT48mDFAdV8Qhxh68fXGvqNcP5IbuwdWuOTtYGNaHbHwIlOUIGXPcs5Oz+yiicaD0e uYyQ== MIME-Version: 1.0 X-Received: by 10.50.152.173 with SMTP id uz13mr6626838igb.106.1361954683012; Wed, 27 Feb 2013 00:44:43 -0800 (PST) Received: by 10.64.26.70 with HTTP; Wed, 27 Feb 2013 00:44:42 -0800 (PST) In-Reply-To: References: Date: Wed, 27 Feb 2013 16:44:42 +0800 Message-ID: Subject: Re: QJM HA and ClusterID From: Azuryy Yu To: user@hadoop.apache.org Content-Type: multipart/alternative; boundary=e89a8f2347e714cd0d04d6b0c976 X-Virus-Checked: Checked by ClamAV on apache.org --e89a8f2347e714cd0d04d6b0c976 Content-Type: text/plain; charset=ISO-8859-1 Patch available now. anybody can take a look, Thanks. On Wed, Feb 27, 2013 at 10:46 AM, Azuryy Yu wrote: > Hi Suresh, > > Thanks for your reply. I filed a bug: > https://issues.apache.org/jira/browse/HDFS-4533 > > > > On Wed, Feb 27, 2013 at 9:30 AM, Suresh Srinivas wrote: > >> looks start-dfs.sh has a bug. It only takes -upgrade option and ignores >> clusterId. >> >> Consider running the command (which is what start-dfs.sh calls): >> bin/hdfs start namenode -upgrade -clusterId >> >> Please file a bug, if you can, for start-dfs.sh bug which ignores >> additional parameters. >> >> >> On Tue, Feb 26, 2013 at 4:50 PM, Azuryy Yu wrote: >> >>> Anybody here? Thanks! >>> >>> >>> On Tue, Feb 26, 2013 at 9:57 AM, Azuryy Yu wrote: >>> >>>> Hi all, >>>> I've stay on this question several days. I want upgrade my cluster from >>>> hadoop-1.0.3 to hadoop-2.0.3-alpha, I've configured QJM successfully. >>>> >>>> How to customize clusterID by myself. It generated a random clusterID >>>> now. >>>> >>>> It doesn't work when I run: >>>> >>>> start-dfs.sh -upgrade -clusterId 12345-test >>>> >>>> Thanks! >>>> >>>> >>> >> >> >> -- >> http://hortonworks.com/download/ >> > > --e89a8f2347e714cd0d04d6b0c976 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Patch available now. anybody can take a look, Thanks.


On Wed, Feb = 27, 2013 at 10:46 AM, Azuryy Yu <azuryyyu@gmail.com> wrote:=
Hi Suresh,
= =A0
Thanks for your reply. I filed a bug: https://issues.apach= e.org/jira/browse/HDFS-4533
=A0


On Wed, Feb 2= 7, 2013 at 9:30 AM, Suresh Srinivas <suresh@hortonworks.com> wrote:
looks start-dfs.sh has a bug. It only tak= es -upgrade option and ignores clusterId.

Consider running the command (which is what start-dfs.sh cal= ls):
bin/hdfs start namenode -upgrade -clusterId <your cluster ID>

Please file a bug, if you can, for start-dfs.sh b= ug which ignores additional parameters.


On Tue, Feb 26, 2013 at 4:5= 0 PM, Azuryy Yu <azuryyyu@gmail.com> wrote:
Anybody here? Thanks!


On Tue, Feb 26, 2013 at 9:57 AM, Azuryy = Yu <azuryyyu@gmail.com> wrote:
Hi all,
I've stay = on this question several days. I want upgrade my cluster from hadoop-1.0.3 = to hadoop-2.0.3-alpha, I've configured QJM successfully.

How to customize clusterID by myself. It generated a random = clusterID now.

It doesn't work when I run:

start-dfs.sh -upgrad= e -clusterId 12345-test

Thanks!

<= /div>




<= font color=3D"#888888">--
http://hortonworks.com/download/


--e89a8f2347e714cd0d04d6b0c976--