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. Regards, -- Ilya Kasnacheev пн, 3 сент. 2018 г. в 17:53, wangsan <[email protected]>: > > 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 restart or > >> alarm or start on anther machine. > > 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 taking down > them > all the time. > > >> In a machine, It will many nodes, When the machine crash. I hope the > >> cluster can work well. > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
