[
https://issues.apache.org/jira/browse/IGNITE-4335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk resolved IGNITE-4335.
--------------------------------------
Resolution: Fixed
This has been implemented as a part of IGNITE-3477
> Implement cluster ACTIVE/INACTIVE state
> ---------------------------------------
>
> Key: IGNITE-4335
> URL: https://issues.apache.org/jira/browse/IGNITE-4335
> Project: Ignite
> Issue Type: New Feature
> Components: general
> Reporter: Alexey Goncharuk
> Fix For: 2.0
>
>
> I think it might be beneficial in some cases to start cluster in some form of
> inactive state. In this case we can skip start of many managers and
> processors (basically, start only discovery + communication), which should
> speed up the cluster start process.
> Once all nodes are started, an API call or a shell command can activate the
> cluster and start all managers in one pass. This should significantly reduce
> traffic, affinity calculations, etc.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
