I agree with Ivan's concern - do we really need the "activation" concept in Ignite?
Activation was introduced with Ignite persistence: we must prevent both the read and write operations on a cluster with persistence on until full data set is loaded (all the nodes are started). Cluster "activation" was a hint to the cluster to know that enough nodes had started for the cluster to have all the data. Then we introduced the concept of "baseline topology". It looks like the "cluster is active" is similar to "cluster has baseline topology defined". Can we remove the concept of "activation" now and leave only "set baseline topology" ? Having duplicate concepts negatively impacts Ignite's usability, making it unnecessary more complex. -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
