Hi, Please take a look at my answers below:
1)Yes. Node filter should be run only on coordinator node after reassignment process. It could be executed several times and possible that Ignite instance can be uninjected. All this behavior should be documented as well as for me. 2) Node filter predicate should be stateless and should always return the same value for the same node. It means that using the compute task in return value as you did isn't correct. As I know there is no direct possibility to see that service deployed/undeployed now. In case if all nodes from nodeFiter were failed then Ignite will wait for them. I found next issue and possible that it could help with it when it will be ready - https://issues.apache.org/jira/browse/IGNITE-8365 You can try to handle the service nodes by their ids and in case if all of them are offline try to do something. BR, Andrei -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/