Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Mon, 21 Mar 2016 17:12:25 +0000 (UTC)
From: "Hudson (JIRA)" <jira@apache.org>
To: issues@ambari.apache.org
Message-ID: <JIRA.12952035.1458567211000.6647.1458580345777@Atlassian.JIRA>
In-Reply-To: <JIRA.12952035.1458567211000@Atlassian.JIRA>
References: <JIRA.12952035.1458567211000@Atlassian.JIRA>
 <JIRA.12952035.1458567211953@arcas>
Subject: [jira] [Commented] (AMBARI-15491) Non NameNode-HA properties still
 in hdfs-site.xml after enabling HA (scripts refer to non-existent property
 values)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/AMBARI-15491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15204640#comment-15204640 ] 

Hudson commented on AMBARI-15491:
---------------------------------

FAILURE: Integrated in Ambari-branch-2.2 #537 (See [https://builds.apache.org/job/Ambari-branch-2.2/537/])
AMBARI-15491. Non NameNode-HA properties still in hdfs-site.xml after (aonishuk: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=0c650bcfafeb6ec0c34328625b378a8eea77740b])
* ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/config-upgrade.xml
* ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/config-upgrade.xml


> Non NameNode-HA properties still in hdfs-site.xml after enabling HA (scripts refer to non-existent property values)
> -------------------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-15491
>                 URL: https://issues.apache.org/jira/browse/AMBARI-15491
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Andrew Onischuk
>            Assignee: Andrew Onischuk
>             Fix For: 2.2.2
>
>         Attachments: AMBARI-15491.patch
>
>
> This is a copy from AMBARI-13946, but I believe it has enough information
> After enabling NameNode-HA, hdfs-site.xml does still contain non-HA
> properties, including  
> dfs.namenode.rpc-address  
> dfs.namenode.http-address  
> dfs.namenode.https-address  
> This cause the balancer to fail with the following symptoms in Balancer:  
> ...
>     
>     
>     
>     15/11/18 15:48:30 INFO balancer.Balancer: namenodes  = [hdfs://daplab2, hdfs://daplab-rt-11.fri.lan:8020]
>     ...
> java.io.IOException: Another Balancer is running.. Exiting ...  
> And ATS:
>     
>     
>     
>     _assert_valid
>         self.target_status = self._get_file_status(target)
>       File "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py", line 292, in _get_file_status
>         list_status = self.util.run_command(target, 'GETFILESTATUS', method='GET', ignore_status_codes=['404'], assertable_result=False)
>       File "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py", line 210, in run_command
>         raise Fail(err_msg)
>     resource_management.core.exceptions.Fail: Execution of 'curl -sS -L -w '%{http_code}' -X GET 'http://pvvsccmn1-brn1:50070/webhdfs/v1/ats/done?op=GETFILESTATUS&user.name=hdfs'' returned status_code=403. 
>     {
>       "RemoteException": {
>         "exception": "StandbyException", 
>         "javaClassName": "org.apache.hadoop.ipc.StandbyException", 
>         "message": "Operation category READ is not supported in state standby"
>       }
>     }
>     
>     
> These should be removed from the config.
> Steps to reproduce:Enable namenode HA on Ambari 2.2
> Expected behavior: after turning on NameNode HA, grep grep dfs.namenode.http-
> address /etc/hadoop/conf/hdfs-site.xml shouldn't return anything


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)