Re: Cleaning up related issue

Is the node with the large volume a new node or an existing node. If it is an existing node is this the one where the node tool cleanup failed. Cheers, Akhil > On 19/06/2017, at 6:40 PM, wxn...@zjqunshuo.com wrote: > > Hi, > After adding a new node, I started cleaning up task to remove the old

Cleaning up related issue

Hi, After adding a new node, I started cleaning up task to remove the old data on the other 4 nodes. All went well except one node. The cleanup takes hours and the Cassandra daemon crashed in the third node. I checked the node and found the crash was because of OOM. The Cassandra data volume has

Re: Question: Behavior of inserting a list multiple times with same timestamp

This is an expected behavior. We learned this issue/feature at the current site (we use Dse 5.08) Subroto > On Jun 18, 2017, at 10:29 PM, Zhongxiang Zheng wrote: > > Hi all, > > I have a question about a behavior when insert a list with specifying > timestamp. > > It is documented that "An

Question: Behavior of inserting a list multiple times with same timestamp

Hi all, I have a question about a behavior when insert a list with specifying timestamp. It is documented that "An INSERT will always replace the entire list." https://github.com/apache/cassandra/blob/trunk/doc/cql3/CQL.textile#lists However, When a list is inserted multiple times using same

Re: Write / read cost of *QUORUM

Hi, yes, you are write. Actually write with QUORUM will cause to coordinator to wait for reply from other nodes, but I guess it's negligible. Best regards, Vladimir Yudovin, Winguzone - Cloud Cassandra Hosting On Sun, 18 Jun 2017 10:07:06 -0400 Jan Algermissen

Write / read cost of *QUORUM

Hi, my understanding is that - for writes using any of the quorum CLs will not put more overall load on the cluster because writes will be sent to all nodes responsible for a partition anyhow. So quorum only increases response time of the coordinator, not cluster load. Correct? - for reads