ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dmitry Lysnichenko (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-15830) Atlas Upgrade Check
Date Tue, 10 May 2016 17:21:13 GMT

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

Dmitry Lysnichenko updated AMBARI-15830:
----------------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

Committed
To https://git-wip-us.apache.org/repos/asf/ambari.git
   f83e258..6c36aa4  trunk -> trunk


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

Mime
View raw message