ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Olexandr K <olexandr.kundire...@gmail.com>
Subject Re: Strange cluster activation behaviour in ignite 2.4.0
Date Thu, 26 Apr 2018 11:16:30 GMT
yes, everything is clear now
thanks!

On Thu, Apr 26, 2018 at 2:05 PM, slava.koptilin <slava.koptilin@gmail.com>
wrote:

> Hi,
>
> 1) start 2 server nodes
>     ^ the cluster was started at the first time. There was no baseline
> topology yet.
>
> 2) control.bat --state => Cluster is inactive
> 3) control.bat --activate => Cluster activated
>     ^ the first activation of the cluster, it forms baseline topology
>
> 4) stop both nodes
> 5) start them again
>     ^ The baseline already exists and Ignite can automatically activate the
> cluster.
>
> 6) control.bat --state => Cluster is active
>     ^ Yes, that is expected behavior.
>
> Please take a look at this page:
> https://apacheignite.readme.io/docs/cluster-activation#
> section-baseline-topology
>
> > Note that the baseline topology is not set when the cluster is started
> for
> > the first time;
> > that's the only time when a manual intervention is needed.
> > So, once all the nodes that should belong to the baseline topology are up
> > and running,
> > you can set the topology from code, Ignite Web Console or command line
> > tool,
> > and let Ignite handle the automatic cluster activation routines going
> > forward.
>
> I hope this hepls.
>
> Thanks,
> Slava.
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Mime
View raw message