You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2016/04/10 00:58:25 UTC

[jira] [Commented] (AMBARI-15788) Ambari upgrade should auto-populate dfs.internal.nameservice

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

Hadoop QA commented on AMBARI-15788:
------------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12797873/AMBARI-15788.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 1 new or modified test files.

    {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:green}+1 core tests{color}.  The patch passed unit tests in ambari-server.

Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/6331//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/6331//console

This message is automatically generated.

> Ambari upgrade should auto-populate dfs.internal.nameservice
> ------------------------------------------------------------
>
>                 Key: AMBARI-15788
>                 URL: https://issues.apache.org/jira/browse/AMBARI-15788
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server, stacks
>    Affects Versions: 2.2.2
>            Reporter: Sumit Mohanty
>            Assignee: Sumit Mohanty
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-15788.patch
>
>
> As part of this task, Ambari upgrade code should be modified to automatically add {{dfs.internal.nameservices}} based on what value exists in {{dfs.nameservices}}. It can be assumed that the value will be valid (not a comma separated string) as if its a working cluster managed by Ambari then {{dfs.nameservices}} cannot contain multiple nameservices.
> Another upgrade task is to modify the alert definitions to switch to the new property.



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