Hi Denis, Thanks for your reply.
> You didn't configure any backups for your cache, so, there is only one > node for every key in the cluster. In order to configure backups for cache, use CacheConfiguration.setBackups(int) method. If i have 3 nodes server, do i have to set up which is the primary and backup nodes? It is like paradigm DBMS Master and Slave? I will put F5 before invoke into my 3 nodes server. So the F5 will become load balancer and also failover. Is it fine? What if i set second node and third nodes to 'Backup', and suddenly first node down, then F5 will pointer to 2nd or 3rd nodes. How about insert/put/update operations will be? Where is the data will be stored? > Another option is to make the cache replicated, but it will make > insert/put/update operations slower. Covered here: > https://apacheignite.readme.io/docs/cache-modes Yes I have implemented replication cache (https://apacheignite.readme.io/docs/cache-modes). > Do you mean, that you connected to different Ignite nodes, using JDBC > driver, and ran queries? yes it is. >In this case you will get the same result, regardless of where the data is stored. In my case, data will be stored at this nodes (IP = 10.5.42.95) right? >> 2. Dbeaver connect to IP = 10.5.42.95 >If some data is missing on a local node, Ignite sends requests to other nodes. I think the data will be stored on each cluster. I was wrong about this. Would you mind to clarification about this... -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
