ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yusaku Sako (JIRA)" <j...@apache.org>
Subject [jira] [Reopened] (AMBARI-9073) Rolling Upgrade - Finalize needs to complete upgrade states in DB
Date Wed, 14 Jan 2015 12:49:35 GMT

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

Yusaku Sako reopened AMBARI-9073:
---------------------------------

Reverted due to server UT failure introduced that was reported via https://builds.apache.org/job/Ambari-trunk-Commit/1474/

> Rolling Upgrade - Finalize needs to complete upgrade states in DB
> -----------------------------------------------------------------
>
>                 Key: AMBARI-9073
>                 URL: https://issues.apache.org/jira/browse/AMBARI-9073
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-server
>    Affects Versions: 2.0.0
>            Reporter: Yurii Shylov
>            Assignee: Yurii Shylov
>             Fix For: 2.0.0
>
>
> This will only make transitions in the DB.
> cluster_version needs to be correct at all times. After the normal execution steps of
the runbook finish, the cluster_version needs to have a state of UPGRADED.
> Similarly, host_version and hostcomponentstate's upgrade_state column need to be correct
at all times. The host_version should have a state of UPGRADED when it has been successful
on a host (because all components on that host have been updated). On the agent hearbeat,
the status command needs to update the currently running version of a component on a host,
in order to update the hostcomponentstate's upgrade_state column (which should only be updated
during an Upgrade); this is needed because the user can ignore errors that occur during the
Rolling Upgrade, so a host may be partially updated.



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

Mime
View raw message