Re: Re: Data export with consistency problem

2016-03-31 Thread Alain RODRIGUEZ
> > If we remove the network cable of one node, import 30 million rows of > data into that table, and then reconnect the network cable, we export the > data immediately and we cannot get all the 30 million rows of data. > But if we manually run ' kill -9 pid' of one node, import 30 million rows > o

Re:Re: Data export with consistency problem

2016-03-25 Thread xutom
Thanks for ur reply! I am so sorry for my poor English. My keyspace replication is 3 and client read and write CL both are QUORUM. If we remove the network cable of one node, import 30 million rows of data into that table, and thenreconnect the network cable, we export the data immediately and we

Re: Data export with consistency problem

2016-03-25 Thread Alain RODRIGUEZ
Hi Jerry, It is all a matter of replication server side and consistency level client side. The minimal setup to ensure availability and a strong consistency is RF= 3 and CL = (LOCAL_)QUORUM. This way, one node can go down, you still can reach the 2 needed nodes to validate your reads & writes --

Data export with consistency problem

2016-03-24 Thread xutom
Hi all, I have a C* cluster with five nodes and my cassandra version is 2.1.1 and we also enable "Hinted Handoff" . Everything is fine while we use C* cluster to store up to 10 billion rows of data. But now we have a problem. During our test, after we import up to 40 billion rows of data int