Hello!
I think you can have a singleton service that periodically checks the
attributes() for all nodes. If anyone is amiss from previous runs, try to
re-start it.
Be sure to use 'exclude neighbours' cache affinity setting when having
multiple server nodes on same machine to avoid data loss.
1. Note that you will have problem writing to caches when topology changes.
Why not just query ignite.cluster(), expose node traits as
node.attributes()?
>> Yes, I use attributes for node join. But I want to know the stopped
>> nodes(when node left) . Then I can do some operations such as
Hello!
1. Note that you will have problem writing to caches when topology changes.
Why not just query ignite.cluster(), expose node traits as
node.attributes()?
2. Having 100 servers should not be a problem. It is recommended to have
long-lived clients in this case, as opposed to creating and
I am using ignite to manage my cluster.when node join I save an item in my
NodeCache, when node left I delete an item in my NodeCache with ignite event
listener.
Use custom NodeCache but not ignite cluster topology,The reason is I want to
keep node status persistence when node left for some
