FYI the issue https://issues.apache.org/jira/browse/IGNITE-8774 is now fixed,
the fix will be available in Ignite 2.7.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
You can restart the cluster. Compatibility mode flag is not stored to PDS,
it exists only in memory.
2018-08-13 9:06 GMT+03:00 arunkjn :
> Thanks Alex,
>
> How can I fix this in the current cluster without resetting the persistence
> state of entire cluster?
>
>
>
> --
> Sent from: http://apache-
Thanks Alex,
How can I fix this in the current cluster without resetting the persistence
state of entire cluster?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi,
I am experiencing the same issue with a ignite 2.5 cluster deployed in
kubernetes.
Scenario:
5 server nodes hosting some caches. They are deployed multiple times without
issues.
I connected a visor client to this cluster (this is the first time i used
visor ever on this cluster)
On another r
Hi, Arun
When daemon node (visor) first time join the cluster it switch the cluster
to compatibility mode. In this mode node containing baseline topology
information will fail to join even if daemon node already leave the
cluster. This issue was fixed by ticket [1] and will be available in Ignite
Hi,
I am experiencing the same issue with a ignite 2.5 cluster deployed in
kubernetes.
Scenario:
5 server nodes hosting some caches. They are deployed multiple times without
issues.
I connected a visor client to this cluster (this is the first time i used
visor ever on this cluster)
On another r
