[
https://issues.apache.org/jira/browse/AMBARI-15491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15204513#comment-15204513
]
Andrew Onischuk commented on AMBARI-15491:
------------------------------------------
This failure doesn't look related to the change. I'm going to commit as is.
Run the tests manually:
{noformat}
[INFO] Rat check: Summary of files. Unapproved: 0 unknown: 0 generated: 0
approved: 141 licence.
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Ambari Views ...................................... SUCCESS [2.946s]
[INFO] Ambari Metrics Common ............................. SUCCESS [0.826s]
[INFO] Ambari Server ..................................... SUCCESS [1:09.868s]
[INFO] Ambari Agent ...................................... SUCCESS [9.697s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1:27.130s
[INFO] Finished at: Mon Mar 21 17:57:33 EET 2016
[INFO] Final Memory: 71M/1382M
[INFO] ------------------------------------------------------------------------
{noformat}
> 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)
