Great , Thank You (
I will try to do it and test it to see how it works.
Thank You again for the clarification .
Vladik
On 5/29/18, 16:08, "aealexsandrov" wrote:
Hi,
I think that it could work. But I think you in case if you see that you
should change the list of nodes
Thank You
The current behavior when it runs only from coordinator is good enough.
I have modified you example to run the predicate on nodes to check for example
some file existence .
I think it stateless but for sure not idempotent .
See below it just returns nodes that has some file on the
Hi,
I checked next code:
Ignite ignite =
IgnitionEx.start("examples/config/example-ignite.xml", "ignite-1");
Ignite ignite2 =
IgnitionEx.start("examples/config/example-ignite.xml", "ignite-2");
ClusterGroup cg = ignite2.cluster().forPredicate(new
IgnitePredicate() {
Thank You.
The issue is that I want to extend the notion of service failures beyond simple
node failure/topology change scenarios.
I already have per Ignite service health check that runs custom health check on
service and redeploys it if necessary obviously this is my custom
implementation.
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
It explains a lot I thought that I am missing something in the docs (
So this is indeed what I see as it executed on the node where the services are
running I think you call it coordinator.
So this behavior is correct it's just need to be fixed in documentation ?
So is there a
Hi,
Indeed there is some unexpected behavior of the how it documented and how it
works.
I filed next issues related to service/cache deploying with node filters:
https://issues.apache.org/jira/browse/IGNITE-8629 - There is no
documentation about what on which node Ignite Predicate will be
Hi,
I am using Ignite 2.4
In the documentation of Node Filter :
https://apacheignite.readme.io/docs/service-grid#section-node-filter-based-deployment
There is following :
“This approach is based on a filtering predicate that gets called on every node
at the time Ignite Service engine
