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 4BD77EAF6 for ; Wed, 27 Feb 2013 01:30:59 +0000 (UTC) Received: (qmail 25689 invoked by uid 500); 27 Feb 2013 01:30:54 -0000 Delivered-To: apmail-hadoop-hdfs-user-archive@hadoop.apache.org Received: (qmail 25575 invoked by uid 500); 27 Feb 2013 01:30:54 -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 25568 invoked by uid 99); 27 Feb 2013 01:30:54 -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 01:30:54 +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.128.45 as permitted sender) Received: from [209.85.128.45] (HELO mail-qe0-f45.google.com) (209.85.128.45) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 Feb 2013 01:30:47 +0000 Received: by mail-qe0-f45.google.com with SMTP id b4so29206qen.4 for ; Tue, 26 Feb 2013 17:30:27 -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=ILIaQ+3s4ExHVYD6OgWLAgu6nlZALkAmqdj7V6F+3jM=; b=FUUxW3gn8cNOHvqjDwCeQF+4Z17KL6WSeNHkF0wvPivXfNocnFjxWAhRsw9TJrvsTq dVxjV8jpC/PFD1X38eb+Z8f5wFWG3AWcNg7A9FE8hmJiGWAyWjhpPfoNH+7ZbXDBZ8X9 rxE7DJN8kn2Zw+3CA8+LmqGahCobWHZ7V1bJ96TOLcOUlTuGlWgCPk8oaIvGXHNUrEpG e+d+2+0Kp2k88lqQ2plLZzdy2Qfiql9cLGvEbnLOoFo9xqwKyhq9naKgLc4lHGwDhoaV cFaZgSXFyVZM08LPQmk/QPDLZ5LLisMb7sdRktZjY93+gtx77Q//jW83SGwprDDzBIxG PcUA== MIME-Version: 1.0 X-Received: by 10.49.127.145 with SMTP id ng17mr686593qeb.25.1361928627147; Tue, 26 Feb 2013 17:30:27 -0800 (PST) Received: by 10.49.29.166 with HTTP; Tue, 26 Feb 2013 17:30:27 -0800 (PST) In-Reply-To: References: Date: Tue, 26 Feb 2013 17:30:27 -0800 Message-ID: Subject: Re: QJM HA and ClusterID From: Suresh Srinivas To: "hdfs-user@hadoop.apache.org" Content-Type: multipart/alternative; boundary=047d7b6dcee007f18204d6aab8e1 X-Gm-Message-State: ALoCoQkvmCh7M1hwNrVDXGdMb3LWhS8CqdU20HqnDqLtzuA9Al/5xpRoaIhNB/N2Zp0e3M7RlaJO X-Virus-Checked: Checked by ClamAV on apache.org --047d7b6dcee007f18204d6aab8e1 Content-Type: text/plain; charset=ISO-8859-1 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/ --047d7b6dcee007f18204d6aab8e1 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
looks start-dfs.sh has a bug. It only takes -upgrade optio= n and ignores clusterId.

Consider running the comm= and (which is what start-dfs.sh calls):
bin/hdfs start name= node -upgrade -clusterId <your cluster ID>

Please file a bug, if you can, for st= art-dfs.sh bug which ignores additional parameters.


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


On Tue, F= eb 26, 2013 at 9:57 AM, Azuryy Yu <azuryyyu@gmail.com> wrot= e:
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.<= br>
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>




--
http://h= ortonworks.com/download/
--047d7b6dcee007f18204d6aab8e1--