Return-Path: X-Original-To: apmail-ambari-dev-archive@www.apache.org Delivered-To: apmail-ambari-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5D7191837F for ; Wed, 6 Jan 2016 20:30:40 +0000 (UTC) Received: (qmail 43545 invoked by uid 500); 6 Jan 2016 20:30:40 -0000 Delivered-To: apmail-ambari-dev-archive@ambari.apache.org Received: (qmail 43503 invoked by uid 500); 6 Jan 2016 20:30:40 -0000 Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ambari.apache.org Delivered-To: mailing list dev@ambari.apache.org Received: (qmail 43462 invoked by uid 99); 6 Jan 2016 20:30:40 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Jan 2016 20:30:40 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id D686E2C1F5D for ; Wed, 6 Jan 2016 20:30:39 +0000 (UTC) Date: Wed, 6 Jan 2016 20:30:39 +0000 (UTC) From: "Matt Foley (JIRA)" To: dev@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (AMBARI-14453) Ambari has lowercase hostnames while cluster is installed with uppercase hostnames. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AMBARI-14453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15086229#comment-15086229 ] Matt Foley commented on AMBARI-14453: ------------------------------------- [~lakshmivs], please clarify why you believe the java.net.ConnectException is due to uppercase/lowercase issues? It is our understanding that on all Linux (including SUSE) and WIndows, hostname resolution is case-insensitive. Hosts generally retain and present the mixed-case form of their own names for human readability, but hostname matching for DNS purposes is done case-insensitive. Anyway by the time you get to "connection refused", you're working with IP addresses already. You may instead have a configuration issue, perhaps due to incomplete configuration for multi-homing. > Ambari has lowercase hostnames while cluster is installed with uppercase hostnames. > ----------------------------------------------------------------------------------- > > Key: AMBARI-14453 > URL: https://issues.apache.org/jira/browse/AMBARI-14453 > Project: Ambari > Issue Type: Bug > Components: ambari-server > Affects Versions: 2.2.0 > Reporter: Lakshmi VS > Assignee: Dmitry Lysnichenko > Fix For: 2.2.1 > > Attachments: Ambari.JPG, hbase-hbase-master-N9-1-1.log, yarn-yarn-resourcemanager-N9-1-1.log > > > Steps followed - > 1. Hadoop cluster with below config is installed successfully with uppercase hostnames. > {code} > CLUSTERNAME='N91' > MASTER1=N9-1-1.labs > MASTER2=N9-1-2.labs > DATANODE1=N9-1-3.labs > DATANODE2=N9-1-4.labs > DATANODE3=N9-1-5.labs > {code} > Snippet of /etc/hosts file - > {code} > 10.0.8.1 N9-1-1.labs N9-1-1 byn001-1 hadoopvm1-1 > 10.0.8.2 N9-1-2.labs N9-1-2 byn001-2 hadoopvm1-2 > 10.0.8.3 N9-1-3.labs N9-1-3 byn001-3 hadoopvm1-3 > 10.0.8.4 N9-1-4.labs N9-1-4 byn001-4 hadoopvm1-4 > 10.0.8.5 N9-1-5.labs N9-1-5 byn001-5 hadoopvm1-5 > {code} > 2. Ambari host page shows all hostnames to be of lower case. > 3. Attempt to run jobs fails on - > {code} > Error: java.net.ConnectException: Call From N9-1-4.labs/10.0.8.4 to n9-1-1.labs:8020 failed on connection exception: java.net.ConnectException: Connection refused; > {code} > Snippet of mapreduce job failure - > {code} > out: 15/12/21 08:12:09 INFO mapreduce.Job: Task Id : attempt_1450702943449_0001_m_000002_0, Status : FAILED > out: Error: java.net.ConnectException: Call From N9-1-4.labs/10.0.8.4 to n9-1-1.labs:8020 failed on connection exception: java.net.ConnectException: Connection refused; For more details see: http://wiki.apache.org/hadoop/ConnectionRefused > out: at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > out: at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > out: at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > out: at java.lang.reflect.Constructor.newInstance(Constructor.java:422) > out: at org.apache.hadoop.net.NetUtils.wrapWithMessage(NetUtils.java:792) > at org.apache.hadoop.net.NetUtils.wrapException(NetUtils.java:732) > at org.apache.hadoop.ipc.Client.call(Client.java:1431) > at org.apache.hadoop.ipc.Client.call(Client.java:1358) > at org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:229) > at com.sun.proxy.$Proxy13.getFileInfo(Unknown Source) > at org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolTranslatorPB.getFileInfo(ClientNamenodeProtocolTranslatorPB.java:771) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.apache.hadoop.io.retry.RetryInvocationHandler.invokeMethod(RetryInvocationHandler.java:252) > at org.apache.hadoop.io.retry.RetryInvocationHandler.invoke(RetryInvocationHandler.java:104) > at com.sun.proxy.$Proxy14.getFileInfo(Unknown Source) > at org.apache.hadoop.hdfs.DFSClient.getFileInfo(DFSClient.java:2116) > at org.apache.hadoop.hdfs.DistributedFileSystem$22.doCall(DistributedFileSystem.java:1315) > at org.apache.hadoop.hdfs.DistributedFileSystem$22.doCall(DistributedFileSystem.java:1311) > at org.apache.hadoop.fs.FileSystemLinkResolver.resolve(FileSystemLinkResolver.java:81) > at org.apache.hadoop.hdfs.DistributedFileSystem.getFileStatus(DistributedFileSystem.java:1311) > at org.apache.hadoop.fs.FileSystem.exists(FileSystem.java:1424) > at org.apache.hadoop.mapreduce.lib.output.FileOutputCommitter.needsTaskCommit(FileOutputCommitter.java:641) > at org.apache.hadoop.mapreduce.lib.output.FileOutputCommitter.needsTaskCommit(FileOutputCommitter.java:630) > at org.apache.hadoop.mapred.Task.isCommitRequired(Task.java:1085) > at org.apache.hadoop.mapred.Task.done(Task.java:1042) > at org.apache.hadoop.mapred.MapTask.run(MapTask.java:345) > at org.apache.hadoop.mapred.YarnChild$2.run(YarnChild.java:168) > at java.security.AccessController.doPrivileged(Native Method) > at javax.security.auth.Subject.doAs(Subject.java:422) > at org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1657) > at org.apache.hadoop.mapred.YarnChild.main(YarnChild.java:162) > Caused by: java.net.ConnectException: Connection refused > at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) > at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717) > at org.apache.hadoop.net.SocketIOWithTimeout.connect(SocketIOWithTimeout.java:206) > at org.apache.hadoop.net.NetUtils.connect(NetUtils.java:531) > at org.apache.hadoop.net.NetUtils.connect(NetUtils.java:495) > at org.apache.hadoop.ipc.Client$Connection.setupConnection(Client.java:612) > at org.apache.hadoop.ipc.Client$Connection.setupIOstreams(Client.java:710) > at org.apache.hadoop.ipc.Client$Connection.access$2800(Client.java:373) > at org.apache.hadoop.ipc.Client.getConnection(Client.java:1493) > at org.apache.hadoop.ipc.Client.call(Client.java:1397) > ... 27 more > {code} > 3. Services - HDFS, Mapreduce, HBase, Yarn services which were up and running after installation go down. > Attached are the logs for Yarn and HBase services. -- This message was sent by Atlassian JIRA (v6.3.4#6332)