Yes I understand it now ( I found the solution to this actually ... Following work : In case if service failed to deploy for some reason for example because there is no eligible nodes . Running cancel for service and then deploy again with same config will trigger the cycle again and actually "force" redeploy. But obviously I am abusing the nodeFilter as you mentioned.
Thank You, Vladik On 5/28/18, 20:10, "aealexsandrov" <[email protected]> wrote: Hi, There is no force deploying/undeploying possibility as I know. As was mentioned in another your question: http://apache-ignite-users.70518.x6.nabble.com/Clarification-regarding-nodeFilter-td21671.html 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 statement as you did isn't correct. Note that nodeFilter predicate is a part of service configuration. So you can't change it after service deployment (add/remove a new node to node filter logic). You should undeploy it fully and deploy with the new configuration (add/remove a new node to node filter logic). BR, Andrei -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
