Re: Strange cluster activation behaviour in ignite 2.4.0

[Olexandr K]

yes, everything is clear now
thanks!

On Thu, Apr 26, 2018 at 2:05 PM, slava.koptilin 
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/
>

Re: Strange cluster activation behaviour in ignite 2.4.0

[slava.koptilin]

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/

Re: Strange cluster activation behaviour in ignite 2.4.0

[Olexandr K]

but I didn't setup baseline topology

doc says: "To form the baseline topology from a set of nodes, use the
./control.sh --baseline set command along with a list of the nodes' consist
ent IDs:"

is it auto-resolving after first cluster activation and we don't need to
use "control.bat --baseline" at all?

On Thu, Apr 26, 2018 at 1:06 PM, slava.koptilin 
wrote:

> Hello Oleks,
>
> The cluster can be automatically activated once all the nodes of the
> baseline topology have joined after a cluster restart. This is expected
> behaviour.
>
> [1]
> https://apacheignite.readme.io/docs/cluster-activation#
> section-automatic-activation
>
> Thanks,
> Slava.
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: Strange cluster activation behaviour in ignite 2.4.0

[slava.koptilin]

Hello Oleks,

The cluster can be automatically activated once all the nodes of the
baseline topology have joined after a cluster restart. This is expected
behaviour.

[1]
https://apacheignite.readme.io/docs/cluster-activation#section-automatic-activation

Thanks,
Slava.



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Strange cluster activation behaviour in ignite 2.4.0

[Mikael]

Silly question, do you have native persistence enabled ?

Mikael

Den 2018-04-26 kl. 11:14, skrev Olexandr K:

Hi Igniters,

I observe strange cluster activation behaviour in ignite 2.4.0

1) start 2 server nodes
2) control.bat --state => Cluster is inactive
3) control.bat --activate => Cluster activated
4) stop both nodes
5) start them again
6) control.bat --state => Cluster is active

Q: why my cluster was auto-activated on restart? Is it expected?

I didn't run any "control.bat --baseline" command

OS : Windows Server 2012 R2


    class="org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi">

                
                
    
    class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder"> 


    

host1:47500..47504
host2:47500..47504
    
    
    
    
    
    

Strange cluster activation behaviour in ignite 2.4.0

[Olexandr K]

Hi Igniters,

I observe strange cluster activation behaviour in ignite 2.4.0

1) start 2 server nodes
2) control.bat --state => Cluster is inactive
3) control.bat --activate => Cluster activated
4) stop both nodes
5) start them again
6) control.bat --state => Cluster is active

Q: why my cluster was auto-activated on restart? Is it expected?

I didn't run any "control.bat --baseline" command

OS : Windows Server 2012 R2










host1:47500..47504
host2:47500..47504