On Tue, Sep 5, 2017 at 10:51 AM, mcherkasov 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
>
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 writte
Hi Mikhail,
I am just trying to understand the behavior of addData method in conjunction
with FULL_SYNC.
If we have just one server node left, then we are not really replicating,
isn't it ? So let's say we have to persist 2 entries, and after 1 write and
replication, one of the server goes down,
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 wrote:
> Hi all,
>
> I am using IgniteDataStreamer to write to a cache. As
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
