On Tue, Sep 5, 2017 at 10:51 AM, mcherkasov <mcherka...@gridgain.com> wrote:
> I think javadoc is the best source for this: > > /** > * Flag indicating that Ignite should wait for write or commit replies > from all nodes. > * This behavior guarantees that whenever any of the atomic or > transactional writes > * complete, all other participating nodes which cache the written data > have been updated. > */ > > so with FULL_SYNC client node will wait for data will be saved on the > primary node and backup node. > if you have REPLICATED cache that means you have 1 primary node and all > other nodes in the cluster > store backups, so in your case, you lost one backup and that's it. Data was > saved. > I don't think this is exactly true. The client node is calling addData(...) method and will not wait for anything, IgniteDataStreamer is completely asynchronous. However, the primary-key server node will wait for the backup server nodes to be updated before responding back to the client. In case of REPLICATED cache, the primary node will wait until all other nodes are updated, so essentially, all nodes are guaranteed to have the latest state. If one of the nodes crashes, then other nodes will still have the state. > > You right that now you have cluster consists of only 1 node, but you can > start a new node or even hundred nodes, > and data will be replicated to all new nodes. > > > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
