ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ramzinator <rami.hamm...@gmail.com>
Subject Cluster Groups with Affinity Behaviour
Date Thu, 13 Apr 2017 14:08:09 GMT
Hi all,

I have a question regarding the behavior of affinity calls with cluster
groups.
Consider the following test:

Test.java
<http://apache-ignite-users.70518.x6.nabble.com/file/n11952/Test.java>  

In the test I have 2 ignite nodes: N1 & N2 belonging to the same topology.
Each with a user attribute: 
N1: ROLE --> role1
N2: ROLE --> role2

When I do:

ClusterGroup clusterGroup = node1.cluster().forAttribute(ROLE, "role2");
node2.compute(clusterGroup).affinityCall(CACHE_NAME, "some key", callable);

I would expect the computation to take place on node2 ONLY since it's the
only node in the Cluster.
However, it seems that the affinity of the cache overrides the clusterGroup
and it proceeds to execute on node 1 regardless of the API of
compute(clusterGroup) which states: 

"All operations on the returned IgniteCompute instance will only include
nodes from this cluster group."

Would appreciate your input on this, and also if anyone has an idea on how I
can do an affinityCall on a specific sub-cluster, it would be a great help.

Another question: Is it possible to specify what nodes a cache can use. So
that I can be sure when doing an affinityCall on the cache, I am sure of the
nodes involves in executing the callable?

Thanks a lot,
Ramzinator





--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Cluster-Groups-with-Affinity-Behaviour-tp11952.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Mime
View raw message