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 EE6FDEBC0 for ; Mon, 25 Feb 2013 07:56:05 +0000 (UTC) Received: (qmail 24221 invoked by uid 500); 25 Feb 2013 07:56:01 -0000 Delivered-To: apmail-hadoop-user-archive@hadoop.apache.org Received: (qmail 23978 invoked by uid 500); 25 Feb 2013 07:56:00 -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 23958 invoked by uid 99); 25 Feb 2013 07:55:59 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 25 Feb 2013 07:55:59 +0000 X-ASF-Spam-Status: No, hits=1.8 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,NORMAL_HTTP_TO_IP,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of yypvsxf19870706@gmail.com designates 209.85.128.41 as permitted sender) Received: from [209.85.128.41] (HELO mail-qe0-f41.google.com) (209.85.128.41) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 25 Feb 2013 07:55:54 +0000 Received: by mail-qe0-f41.google.com with SMTP id 7so1406224qeb.14 for ; Sun, 24 Feb 2013 23:55:34 -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=ALu2IkrtaqkWyQjQvk9Ijnb5UiRpmVUZL9KALlu69KQ=; b=LZg0y3WdGX4RhDyQBpwDCqObCR/v2bjSDSP6jjXWJN09SUkD5VLvGf0qBCGHPJzAdc xnn2OcFFMnPoXkT8taP9Cw9Db9c9CxDWuxXcLXHQPPAu2ueGFDXrc7ieTiOxNiDP5BlH gyzGmjtCXDPxw5t+IQk0M+9m/J4WFXItELuBAYEyJRhS5A9d/4bnMugYYb2oI1wUTYtT f5ct3H9imAI8TmFuMLWsMYpudUT4lSukRfsXTV4OsWd7J6X5XexN+zoru2B440hlKtlG 6CudttAbZWIG2jqCLRad/iLgtYlic4PMB0iF52LDcfO8Nq0jmHUvZhe/iHC19D5Mtbag gwVw== MIME-Version: 1.0 X-Received: by 10.229.78.80 with SMTP id j16mr2345514qck.87.1361778934089; Sun, 24 Feb 2013 23:55:34 -0800 (PST) Received: by 10.49.82.202 with HTTP; Sun, 24 Feb 2013 23:55:33 -0800 (PST) In-Reply-To: References: Date: Mon, 25 Feb 2013 15:55:33 +0800 Message-ID: Subject: Re: Errors come out when starting Balancer From: YouPeng Yang To: user@hadoop.apache.org Content-Type: multipart/alternative; boundary=002354333326a1074904d687dd5a X-Virus-Checked: Checked by ClamAV on apache.org --002354333326a1074904d687dd5a Content-Type: text/plain; charset=ISO-8859-1 Hi That is great helpfull.Thank you very much. regards 2013/2/25 Harsh J > Hi, > > A few points: > > - The property "fs.default.name" has been deprecated in favor of the > newer name "fs.defaultFS". > - When using nameservice IDs, you shouldn't rely on the RPC address. > That is, your fs.defaultFS should instead simply be "hdfs://ns1", and > the config will load the right RPC that is bound to that NS > automatically from the hdfs-site.xml. > > On Mon, Feb 25, 2013 at 10:35 AM, YouPeng Yang > wrote: > > Hi . > > Sorry to bother you againt. > > > > I need to close this question by myself. > > Here is my core-site.xml: > > ****************************************************************** > > > > > > fs.default.name > > hdfs://Hadoop01:8020 > > > > > > ****************************************************************** > > my hdfs-site.xml: > > ********************************************************************* > > > > > > dfs.nameservices > > ns1,ns2 > > > > > > dfs.namenode.rpc-address.ns1 > > Hadoop01:8040 > > > > .... Other common configuration ... > > > > ********************************************************************** > > > > When start the balancer,the script using the fs.default.name of > > core-site.xml by defulat. > > according to hdfs-site.xml,the port 8020 does no start.So it goes fo fail > > when i start the balancer usig the port 8020 of core-site.xml. > > > > So the ports of fs.default.name and > > dfs.namenode.rpc-address. shoud be consistent. > > > > > > Thanks > > > > Regards > > > > > > > > > > > > 2013/2/24 YouPeng Yang > >> > >> Hi ALL > >> > >> I start the Balancer on the HDFS Federation,however it comes an > error: > >> java.net.ConnectException: Call From Hadoop01/10.167.14.221 to > >> Hadoop01:8020 failed on connection exception: java.net.ConnectException: > >> Connection refused; For more details see: > >> http://wiki.apache.org/hadoop/ConnectionRefused. Exiting ... > >> Balancing took 11.163 seconds > >> > >> How Can i solve this. > >> > >> By the way,I have done what explained on the > >> http://wiki.apache.org/hadoop/ConnectionRefused when i build my basic > and > >> original HDFS cluster.So i think the above error maybe because of > another > >> reasons. > >> > >> thanks > >> > >> Regards. > >> > > > > > > -- > Harsh J > --002354333326a1074904d687dd5a Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi=A0
=A0 =A0That is =A0great helpfull.Thank you= very much.

regards


2013/2/25 Harsh J <harsh@cloudera.com>
Hi,

A few points:

- The property "f= s.default.name" has been deprecated in favor of the
newer name "fs.defaultFS".
- When using nameservice IDs, you shouldn't rely on the RPC address. That is, your fs.defaultFS should instead simply be "hdfs://ns1",= and
the config will load the right RPC that is bound to that NS
automatically from the hdfs-site.xml.

On Mon, Feb 25, 2013 at 10:35 AM, YouPeng Yang
<yypvsxf19870706@gmail.com<= /a>> wrote:
> Hi .
> =A0 Sorry to bother you againt.
>
> =A0 I need to close this question =A0by myself.
> =A0 Here is my core-site.xml:
> =A0 ******************************************************************=
> =A0 <configuration>
> =A0 =A0<property>
> =A0 =A0<name>fs.default.name</name>
> =A0 =A0<value>hdfs://Hadoop01:8020</value>
> =A0 </property>
> =A0</configuration>
> =A0 ******************************************************************=
> =A0my hdfs-site.xml:
> =A0*******************************************************************= **
> <configuration>
> =A0 =A0 <property>
> =A0 =A0 =A0 =A0<name>dfs.nameservices</name>
> =A0 =A0 =A0 =A0<value>ns1,ns2</value>
> =A0 =A0</property>
> =A0 =A0<property>
> =A0 =A0 =A0 =A0<name>dfs.namenode.rpc-address.ns1</name> > =A0 =A0 =A0 <value>Hadoop01:8040</value>
> =A0 =A0</property>
> .... Other common configuration ...
> </configuration>
> **********************************************************************=
>
> When start the =A0balancer,the script using the =A0 fs.default.name of
> core-site.xml by defulat.
> according to hdfs-site.xml,the port 8020 does no start.So it goes fo f= ail
> when i start the balancer usig the port 8020 of core-site.xml.
>
> So the =A0ports of =A0fs.default.name and
> dfs.namenode.rpc-address.<nameserviceid> shoud be consistent. >
>
> Thanks
>
> Regards
>
>
>
>
>
> 2013/2/24 YouPeng Yang <yypvsxf19870706@gmail.com>
>>
>> Hi ALL
>>
>> =A0 I start the =A0Balancer on the HDFS Federation,however it come= s an error:
>> java.net.ConnectException: Call From Hadoop01/10.167.14.221 to
>> Hadoop01:8020 failed on connection exception: java.net.ConnectExce= ption:
>> Connection refused; For more details see:
>> http://wiki.apache.org/hadoop/ConnectionRefused. =A0Exiting= ...
>> Balancing took 11.163 seconds
>>
>> =A0How Can i solve this.
>>
>> By the way,I have done what explained on the
>> http://wiki.apache.org/hadoop/ConnectionRefused =A0when i b= uild my basic and
>> original HDFS cluster.So i think the above error maybe because of = another
>> reasons.
>>
>> thanks
>>
>> Regards.
>>
>



--
Harsh J

--002354333326a1074904d687dd5a--