ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Di Li (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-20461) override_uid should set to false when upgrading Ambari 2.1 to 2.2 or newer with custom stacks
Date Wed, 15 Mar 2017 16:41:41 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-20461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Di Li updated AMBARI-20461:
---------------------------
    Affects Version/s: trunk

> override_uid should set to false when upgrading Ambari 2.1 to 2.2 or newer with custom
stacks
> ---------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-20461
>                 URL: https://issues.apache.org/jira/browse/AMBARI-20461
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: trunk
>            Reporter: Di Li
>            Assignee: Di Li
>             Fix For: trunk
>
>         Attachments: AMBARI-20461.patch
>
>
> Custom stacks may not have override_hbase_uid property in hbase-env.xml, in this case,
override_uid is currently set to true by Ambari's auto merge logic. it should be set to false
when upgrading Ambari 2.1 to 2.2 or newer with custom stacks in order to respect the existing
UID customers already set on their clusters.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message