ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-13946) Non NameNode-HA properties still in hdfs-site.xml causing (at least) Balancer and ATS to fail
Date Thu, 25 Feb 2016 22:40:18 GMT

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

Hudson commented on AMBARI-13946:
---------------------------------

ABORTED: Integrated in Ambari-trunk-Commit #4389 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4389/])
AMBARI-13946. Non NameNode-HA properties still in hdfs-site.xml causing (akovalenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=e4aeab5f870cedfe3c97c75e126e856176c5f46b])
* ambari-web/app/controllers/main/admin/highAvailability/nameNode/step3_controller.js


> Non NameNode-HA properties still in hdfs-site.xml causing (at least) Balancer and ATS
to fail
> ---------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-13946
>                 URL: https://issues.apache.org/jira/browse/AMBARI-13946
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.1.2, 2.2.0
>         Environment: CentOS6.7, HDP2.3-2950
>            Reporter: Benoit Perroud
>            Assignee: Aleksandr Kovalenko
>         Attachments: AMBARI-13946.patch, AMBARI-13946_branch-2.2.patch
>
>
> 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:
> {code}
> ...
> 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 ...
> {code}
> And ATS:
> {code}
> _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"
>   }
> }
> {code}
> These should be removed from the config.
> Steps to reproduce: after turning on NameNode HA, {{grep dfs.namenode.rpc-address|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)

Mime
View raw message