incubator-ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Devaraj Das (Created) (JIRA)" <j...@apache.org>
Subject [jira] [Created] (AMBARI-94) Need to have the cluster-revision-number in the NodeState
Date Fri, 21 Oct 2011 22:00:34 GMT
Need to have the cluster-revision-number in the NodeState
---------------------------------------------------------

                 Key: AMBARI-94
                 URL: https://issues.apache.org/jira/browse/AMBARI-94
             Project: Ambari
          Issue Type: Improvement
            Reporter: Devaraj Das
            Assignee: vitthal (Suhas) Gogate
             Fix For: 0.1.0


Since we want to support the case of simple stack-definition/cluster-definition changes while
the cluster is active,  we need to store the cluster rev# so that when the agent comes with
a heartbeat, the Controller can take smart diffs based on the cluster revision number.

Example: Node1 belongs to {cluster-ID-10, cluster-rev-100}
Now someone changes the cluster's definition to include a new node. This causes the revision#
change to cluster-rev-101.

Unless the Controller stored the cluster-rev for Node1, upon receipt of a heartbeat, the Controller
wouldn't be able to determine what Node1 would need to run to get to the cluster-rev-101 state
(in this case nothing).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message