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
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
Hi,
I have cluster singleton service defined with nodeFilter and background thread
that periodically checks service health.
In case my health check fails it tries to re-deploy service using undeploy and
deploy API.
In general it works great but in case that there is some temporary issue on all
