ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alexey Dmitriev <admitr...@gridgain.com>
Subject Re: Cluster auto activation design proposal
Date Fri, 18 Aug 2017 17:18:51 GMT
API is proposed in the head of the thread by Sergey, as I understood:
______________________________________________________

API for BaselineTopology manipulation may look like this: 

*Ignite::activation::establishBaselineTopology();* 
*Ignite::activation::establishBaselineTopology(BaselineTopology bltTop);* 

Both methods will establish BT and activate cluster once it is established. 

The first one allows user to establish BT using current topology. If any 
changes happen to the topology during establishing process, user will be 
notified and allowed to proceed or abort the procedure. 

Second method allows to use some monitoring'n'management tools like 
WebConsole where user can prepare a list of nodes, using them create a BT 
and send to the cluster a command to finally establish it. 

>From high level BaselineTopology entity contains only collection of nodes: 

*BaselineTopology {* 
*  Collection<TopologyNode> nodes;* 
*}* 

*TopologyNode* here contains information about node - its consistent id and 
set of user attributes used to calculate affinity function. 
____________________________________________



--
View this message in context: http://apache-ignite-developers.2346864.n4.nabble.com/Cluster-auto-activation-design-proposal-tp20295p21066.html
Sent from the Apache Ignite Developers mailing list archive at Nabble.com.

Mime
View raw message