ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nate Cole (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-21059) Reduce Dependency on Cluster Desired Stack ID
Date Thu, 18 May 2017 13:54:04 GMT

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

Nate Cole updated AMBARI-21059:
-------------------------------
    Attachment: AMBARI-21059.patch

> Reduce Dependency on Cluster Desired Stack ID
> ---------------------------------------------
>
>                 Key: AMBARI-21059
>                 URL: https://issues.apache.org/jira/browse/AMBARI-21059
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-server
>            Reporter: Nate Cole
>            Assignee: Nate Cole
>            Priority: Critical
>             Fix For: 3.0.0
>
>         Attachments: AMBARI-21059.patch
>
>
> With the advent of {{PATCH}} and {{CLUSTER}} upgrades, there is no longer the notion
of a cluster being bound to a specific stack. Instead, the stack ID is being pushed down to
the service and component level.
> Currently, upgrades tries to set the cluster desired stack ID on finalization. Eventually
there will be a complete decouple of the cluster from a singular stack id.  This jira covers
a majority of cases in code.  Until configs are refactored, we can't remove the associated
stack id in its entirety.



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

Mime
View raw message