You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ambari.apache.org by "Alejandro Fernandez (JIRA)" <ji...@apache.org> on 2015/01/22 00:39:34 UTC

[jira] [Updated] (AMBARI-9225) RU - Handle components that don't advertise a version when propagation HostComponentState through ClusterVersion, and handle ClusterVersion and HostVersion state transitions correctly

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

Alejandro Fernandez updated AMBARI-9225:
----------------------------------------
    Summary: RU - Handle components that don't advertise a version when propagation HostComponentState through ClusterVersion, and handle ClusterVersion and HostVersion state transitions correctly  (was: RU - Handle components that don't advertise a version when propagation HostComponentState through ClusterVersion)

> RU - Handle components that don't advertise a version when propagation HostComponentState through ClusterVersion, and handle ClusterVersion and HostVersion state transitions correctly
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-9225
>                 URL: https://issues.apache.org/jira/browse/AMBARI-9225
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.0.0
>            Reporter: Alejandro Fernandez
>            Assignee: Alejandro Fernandez
>             Fix For: 2.0.0
>
>         Attachments: AMBARI-9225.v2.patch
>
>
> Finalize requires all components to advertise a version, usually by calling hdp-select. However, AMS (Metric Collector and Metric Monitor), Kerberos, and ZKFC don't advertise a version.
> Further, the transitions of the HostVersion and ClusterVersion need to go through UPGRADING->UPGRADED->CURRENT for a brand new cluster.
> And for a Rolling Upgrade, it needs to go through INSTALLING->INSTALLED->UPGRADING->UPGRADED->CURRENT.



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