Hello!
Please note that ClusterGroups usually do not recompute. This means, if you
had two nodes with _roleAttribute "True", and they all went away, the group
is now empty, even as two new nodes has joined with the same attribute.
You need to re-create ClusterGroup in order to refresh it.
Using ignite reference is completely fine.
What is the exact exception being thrown in this case? I would expect to see
this if the node is out of topology, what does the logs tell? Do other nodes
see this one in the topology?
Please check if there are NODE_FAILED events for the node on other
I've been researching a problem where we see a ClusterGroup topology
becoming unexpectedly empty. I have not found anything that is similar to
my case outlined below:
We have some code using the C# client on Ignite 2.8.0 like this:
var _group = _ignite?.GetCluster()?.ForAttribute(_roleAttribute,
