title: Ignite - full sync configuration
body: <p>I have two server ignite nodes (Each node is started in the Spring Boot application) in the cluster.</p>
  
  <p>And i have two cache: </p>
  
  <p>//Persistence cahce</p>
  
  <pre><code>configuration.setReadThrough(true);
      configuration.setWriteThrough(true);
      configuration.setCacheStoreFactory(storeFactory);
      configuration.setAtomicityMode(CacheAtomicityMode.TRANSACTIONAL);
      configuration.setWriteSynchronizationMode(CacheWriteSynchronizationMode.FULL_SYNC);
      configuration.setCacheMode(CacheMode.REPLICATED);
  </code></pre>
  
  <p>//in memory </p>
  
  <pre><code>configuration.setIndexedTypes(String.class, SequenceReserve.class);
      configuration.setAtomicityMode(CacheAtomicityMode.TRANSACTIONAL);
      configuration.setWriteSynchronizationMode(CacheWriteSynchronizationMode.FULL_SYNC);
      configuration.setCacheMode(CacheMode.REPLICATED);
  </code></pre>
  
  <p>Requests for update to any caches can go to each node in parallel.</p>
  
  <p>Every update - atomic operation.</p>
  
  <pre><code>cache.invoke(...);
  </code></pre>
  
  <p>My main goal is to avoid a inconsistent data any cost. In memory cache can get lost, but should not be inconsistent.</p>
  
  <p>Any node should return an exception if the transaction was not commit on all nodes. </p>
  
  <p>Can I write such a configuration that this behavior is guaranteed with 100% probability.</p>
  
  <p><strong>UPDATED</strong></p>
  
  <p>I ran the test and got the following behavior:</p>
  
  <p>Each request is always performed on the same node (invoke method). I believe this is correct behavior. When will the query be executed on the second node?</p>