You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Dmitry Lysnichenko (JIRA)" <ji...@apache.org> on 2016/05/10 17:21:12 UTC

[jira] [Assigned] (AMBARI-15830) Atlas Upgrade Check

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

Dmitry Lysnichenko reassigned AMBARI-15830:
-------------------------------------------

    Assignee: Dmitry Lysnichenko

> Atlas Upgrade Check
> -------------------
>
>                 Key: AMBARI-15830
>                 URL: https://issues.apache.org/jira/browse/AMBARI-15830
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.4.0
>            Reporter: Dmytro Grinenko
>            Assignee: Dmitry Lysnichenko
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-15830.patch, AMBARI-15830.patch.1
>
>
> Atlas for HDP 2.5 will need to be a new install. Atlas does not support upgrade (rolling upgrade or otherwise) from prior versions. It is only from HDP 2.5 on that Atlas support express and rolling upgrades.
> Because of this, it is necessary to have a pre upgrade check in Ambari that handles this case by asking the user to uninstall Atlas prior to upgrade. After the cluster has been upgraded, Atlas can be added to the cluster using the Ambari add service mechanism. This will result in a clean/new install of Atlas that will from this point on support rolling and express upgrades.



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