Hi, it works as expected, with REPLICATED cache you can't lose you data while you have at least 1 server node alive.
Why do you think it should throw an exception? Thanks, Mikhail. On Tue, Sep 5, 2017 at 5:05 PM, userx <[email protected]> wrote: > Hi all, > > I am using IgniteDataStreamer to write to a cache. As a part of my testing, > I started 2 servers on a local node and 1 client locally. I put everything > in debug mode in eclipse, and put a debug point where I am calling > IgniteDataStreamer.addData(). After that i let 2-3 entries to be written to > the cache, I then stop at the same debug point before I let it write the > next entry. Just at that time, I kill one of the two servers (I see some > java.net.SocketException in the client log) and then let the client > continue > to write rest of the entries, since one of the servers is still running. In > spite of the fact that my cache is in 'REPLICATED' mode and the > cachesyncwrite mode is FULL_SYNC, addData method did not throw an exception > and completed successfully. > > Why should it be possible with the given cache modes ? FULL_SYNC shouldn't > let it complete if one of the servers go down, isn't it ? > > > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ > -- Thanks, Mikhail.
