You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Sumit Mohanty (JIRA)" <ji...@apache.org> on 2016/04/09 17:53:25 UTC
[jira] [Updated] (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:all-tabpanel ]
Sumit Mohanty updated AMBARI-15788:
-----------------------------------
Attachment: AMBARI-15788.patch
> 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)