Re: WriteTimeoutException When only One Node is Down

2017-01-15 Thread Shalom Sagges
Hi Yuji, Thanks for your reply. That's what I don't understand. Since the writes are in LOCAL_QUORUM, even if a node fails, there should be enough replica to satisfy the request, shouldn't it? Otherwise, the whole idea behind no single point of failure is only partially true? Or is there something

Re: WriteTimeoutException When only One Node is Down

2017-01-12 Thread Yuji Ito
Hi Shalom, I also got WriteTimeoutException in my destructive test like your test. When did you drop a node? A coordinator node sends a write request to all replicas. When one of nodes was down while the request is executed, sometimes WriteTimeOutException happens. cf. http://www.datastax.com/de

WriteTimeoutException When only One Node is Down

2017-01-11 Thread Shalom Sagges
Hi Everyone, I'm using C* v3.0.9 for a cluster of 3 DCs with RF 3 in each DC. All read/write queries are set to consistency LOCAL_QUORUM. The relevant keyspace is built as follows: *CREATE KEYSPACE mykeyspace WITH replication = {'class': 'NetworkTopologyStrategy', 'DC1': '3', 'DC2': '3', 'DC3': '