ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dmytro Sen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-15788) Ambari upgrade should auto-populate dfs.internal.nameservice
Date Thu, 14 Apr 2016 14:34:25 GMT

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

Dmytro Sen commented on AMBARI-15788:
-------------------------------------

+1

Committed to trunk

> 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)

Mime
View raw message