Reputation: 3262
In mutinode lets say N1, N2 and N3. I have been directly hitting to the node N1 but what happens is hazelcast communicates to N2 and N3 for some reason. Its not an Heart beat check since its configured for 1 min, But I observed using the wireshark, it clearly shows that the call goes to another node (i.e) from N1 to N2.
It clearly shows that when I hit a query to N1, that query is transmitted to N2. I saw the query and data received in wireshark.
Am pretty confused why its happening, All the data's has to be there in Node 1, But why its going to another node for fetching the data?
Thanks, Harry
Upvotes: 5
Views: 274
Reputation: 6094
Data in Hazelcast is partitioned, therefore it doesn't matter to what node you add the data, there is no guarantee that the record will be stored on this node. That means there is communication going on to store / read data in a partitioned fashion. You probably want to read on data partitioning: http://docs.hazelcast.org/docs/3.6/manual/html-single/index.html#data-partitioning
Upvotes: 6