[ https://issues.apache.org/jira/browse/AMBARI-15491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15204358#comment-15204358 ]
Hadoop QA commented on AMBARI-15491:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12794509/AMBARI-15491.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include any new or modified tests.
Please justify why no new tests are needed for this patch.
Also please list what manual steps were performed to verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase the total number of release audit warnings.
{color:red}-1 core tests{color}. The test build failed in ambari-server
Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/5947//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/5947//console
This message is automatically generated.
> 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)