You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Stanilovsky Evgeny (JIRA)" <ji...@apache.org> on 2017/06/21 12:27:00 UTC

[jira] [Resolved] (IGNITE-5568) setActiveOnStart have no effect on node startup

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

Stanilovsky Evgeny resolved IGNITE-5568.
----------------------------------------
    Resolution: Not A Problem

not a bug, node with persistence configuration, starts as inactive independent on _activeOnStart_ flag configuration. After node or nodes started you must explicit activate cluster. This flag makes sense only for the first node in topology, any other node will get state from cluster during join process.

> setActiveOnStart have no effect on node startup
> -----------------------------------------------
>
>                 Key: IGNITE-5568
>                 URL: https://issues.apache.org/jira/browse/IGNITE-5568
>             Project: Ignite
>          Issue Type: Bug
>          Components: cache
>    Affects Versions: 2.0
>            Reporter: Stanilovsky Evgeny
>            Assignee: Stanilovsky Evgeny
>             Fix For: 2.1
>
>         Attachments: 2.1.1_persist_activestart.tar.gz
>
>
> {code}
>         icfg.setActiveOnStart(true);
>         Ignite ignite = Ignition.start(icfg);
> {code}
> brings to:
> Exception in thread "main" class org.apache.ignite.IgniteException: Can not perform the operation because the cluster is inactive.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)