Plus I monitor those Events too:
EVT_NODE_JOINED,
EVT_NODE_LEFT,
EVT_NODE_FAILED,
EVT_NODE_SEGMENTEDSeem the primary partitions support by local node is still
wrong. Every time I bring up ignite instance print:for (int part :
ignite.affinity(IG_CACHE_NAME).primaryPartitions(ignite.cluster().localNode()))
{
logger.error("Init Primary: {}", part);
}And after node events trigger, I print it again:for (int part :
ignite.affinity(IG_CACHE_NAME).primaryPartitions(ignite.cluster().localNode()))
{
logger.error("Current Primary: {}", part);
}and have 3 nodes with partitions number 16, bring up them and kill and
re-bring up , the primary partitions seem never match, between no
EVT_CACHE_REBALANCE* events received. 1, Bring them up one by one A:
Init Primary: 0
Init Primary: 1
Init Primary: 2
Init Primary: 3
Init Primary: 4
Init Primary: 5
Init Primary: 6
Init Primary: 7
Init Primary: 8
Init Primary: 9
Init Primary: 10
Init Primary: 11
Init Primary: 12
Init Primary: 13
Init Primary: 14
Init Primary: 15
B Join
Noting change
C: Join A:
Current Primary: 1
Current Primary: 2
Current Primary: 3
Current Primary: 4
Current Primary: 6
Current Primary: 8
Current Primary: 9
Current Primary: 10
Current Primary: 11
Current Primary: 12
Current Primary: 13
Current Primary: 14
B:
Current Primary: 0
Current Primary: 5
Current Primary: 7
Current Primary: 15
C:
Nothing change
------------------------
2. KILL A:
B:
Current Primary: 0
Current Primary: 5
Current Primary: 7
C:
Current Primary: 10
Current Primary: 14
Current Primary: 15
-----------------------
3. KILL B:
C:
Current Primary: 2
Current Primary: 10
Current Primary: 12
Current Primary: 13
Current Primary: 14
Current Primary: 15
----------------------
4. Bring up B:
B:
Init Primary: 0
Init Primary: 1
Init Primary: 2
Init Primary: 3
Init Primary: 4
Init Primary: 5
Init Primary: 6
Init Primary: 8
Init Primary: 9
Init Primary: 11
Init Primary: 12
Init Primary: 13
C:
Current Primary: 0
Current Primary: 1
Current Primary: 2
Current Primary: 3
Current Primary: 4
Current Primary: 5
Current Primary: 6
Current Primary: 7
Current Primary: 8
Current Primary: 9
Current Primary: 10
Current Primary: 11
Current Primary: 12
Current Primary: 13
Current Primary: 14
Current Primary: 15
----------------------
5. Bring up A:
A:Nothing print
B:
Current Primary: 0
Current Primary: 1
Current Primary: 2
Current Primary: 3
Current Primary: 4
Current Primary: 5
Current Primary: 6
Current Primary: 8
Current Primary: 9
Current Primary: 11
Current Primary: 12
Current Primary: 13
C:
Current Primary: 7
Current Primary: 10
Current Primary: 14
Current Primary: 15
Regards
Aaron
[email protected]
From: [email protected]
Date: 2017-10-19 10:48
To: user
Subject: Re: Re: Where can we get the partition assignment of a Cache after the
cluster changed?
hi Slava,
I monitor all those events:
EVT_CACHE_REBALANCE_PART_LOADED,
EVT_CACHE_REBALANCE_PART_UNLOADED,
EVT_CACHE_REBALANCE_STARTED,
EVT_CACHE_REBALANCE_STOPPED
And found when I start multiple nodes, neither of those events be triggered.
my cache work as PARTITIONED.
But if I monitor the EVT_NODE_JOINED, I can find the node joined, so now the
first node still carry all the primary partitions.
This is not what we expected, we want those two nodes to do load balance, so
when exactly the REBALANCE started?
Regards
Aaron
[email protected]
From: [email protected]
Date: 2017-10-18 19:23
To: user
Subject: Re: Re: Where can we get the partition assignment of a Cache after the
cluster changed?
Got thanks Slava!
[email protected]
From: slava.koptilin
Date: 2017-10-18 17:52
To: user
Subject: Re: Where can we get the partition assignment of a Cache after the
cluster changed?
Hi Aaron,
Please take a look at the following event types:
- EventType#EVT_CACHE_REBALANCE_PART_LOADED [1]
- EventType#EVT_CACHE_REBALANCE_PART_UNLOADED [2]
[1]
https://ignite.apache.org/releases/2.2.0/javadoc/org/apache/ignite/events/EventType.html#EVT_CACHE_REBALANCE_PART_LOADED
[2]
https://ignite.apache.org/releases/2.2.0/javadoc/org/apache/ignite/events/EventType.html#EVT_CACHE_REBALANCE_PART_UNLOADED
Thanks!
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
