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 =>
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
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
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://apac
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 => C
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 m
