You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Alexey Goncharuk (JIRA)" <ji...@apache.org> on 2017/04/10 08:43:41 UTC

[jira] [Closed] (IGNITE-4335) Implement cluster ACTIVE/INACTIVE state

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

Alexey Goncharuk closed IGNITE-4335.
------------------------------------

> 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)