OK. I'm making a system that detects fault from continuous sensor data message.
A Ignite client node named 'Distributor' receives messages from senders and distributes messages to Ignite server nodes by using Ignite (ordered) messaging. Each senders have their own ID(Integer) so they sends ID attached messages. I'm using the sender's ID as a partition number of Grid cache. I'm using each server node's UUID as a messaging topic and the Distributor decides a topic for message by checking which server node has the primary local partitions(= sender's ID). If server node receives message they are queuing messages to parse and execute, therefore a server node fails, queued messages are missing. My customer needs for my system to guarantee no missing message, the Distributor also puts messages to Grid cache by using the IgniteDataStreamer for backup. If a node fails then the cache rebalance will occur, each server node checks their local primary partitions again for what partitions are added to them, then recover missed messages by getting from Grid cache only for locally added primary partitions. At the same time, the Distributor detects server node's primary partitions are changed then remap the destination topics for sender's ID(=partition number). Actually, getting from grid cache is needed only for a time of fail-over. I just need that server nodes can detect which partitions are added as local primary partition to get messages from grid cache with affinity(partition number) and the Distributor can map sender's ID to right topic. This is my story, Anyway, The thing I want to ask you is why the Ignite event 'EVT_CACHE_REBALANCE_STOPPED' is triggered although the actual rebalance is not finished yet. What does this event stands for? The another events like 'EVT_TASK_FINISHED', 'EVT_CACHE_OBJECT_PUT', 'EVT_CACHE_OBJECT_REMOVED' are working well as they named. Sincerely, Andrew. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/How-do-I-know-the-cache-rebalance-is-finished-tp5219p5351.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
