Re: Cassandra table definition with no clustering key

I think this note in the partition key section is what you might be looking for? "Note that a table always has a partition key, and that if the table has no clustering columns, then every partition of that table is only comprised of a single row (since the primary key uniquely identifies rows and

Cassandra table definition with no clustering key

Hi all, I'm trying to understand the scenario when no clustering key is specified in a table definition. If a table has only a partition key and no clustering key, what order the rows under the same partition are stored in? Is it even allowed to have multiple rows under the same partition when

Re: Reversed read write performance.

Nodetool compactionstats Regarding cassandra-stress, make sure that you initiate load outside of database subnet Subroto > On Jul 14, 2017, at 3:02 PM, Roger Warner wrote: > > 30G java heap. The dataset is the usual Cassandra-test size > > How do I tell if

Re: Reversed read write performance.

30G java heap. The dataset is the usual Cassandra-test size How do I tell if compaction has completed? I will add more iterations/time to the test. Thank you Date: Friday, July 14, 2017 at 2:21 PM To: Roger Warner Subject: Re: Reversed read write performance. Pls

Reversed read write performance.

I’m confused about read vs write performance. I was expecting to see higher write than read perf. I’m seeing the opposite by nearly 2X Please help. Am I doing/configuring something wrong or do I have the wrong expectations. I am very new to Cassandra. And this is not using Datastax. .

Re: Cassandra seems slow when having many read operations

Hi Petrus, thanks for the feedback. I couldn't found the percent repaired in nodetool info, C* version is 2.1.8, maybe it's something newer than that? I'm analyzing this thread about num_token. Compaction is "compaction_throughput_mb_per_sec: 16", I don't get pending compactions in Opscenter.

Cassandra Node keep going down

We are using Cassandra 3.x version.. Recently, our production database is going through some instability issues. One of our node is keep going down from every 2 days up to a few of times a day. The node is down due to JVM out of memory. According to my investigation, I suspect that this might

Re: first node in a cluster - should it be a seed node

No, any node can be seed node. But to start the cluster and nodes addition you need some node as seed node. Make sure to include at least one node from each DC as seed. DO NOT make all nodes as seed. > On Jul 14, 2017, at 10:08 AM, Vikram Goyal G > wrote: > >

first node in a cluster - should it be a seed node

Hello, Can you please comment if first node in a cluster must be a seed node. Is it mandatory or not? How will it behave Regards, Vikram

Re: adding nodes to a cluster and changing rf

Increasing RF will result in nodes that previously didn't have a replica of the data now being responsible for it. This means that a repair is required after increasing the RF. Until the repair completes you will suffer from inconsistencies in data. For example, in a 3 node cluster with RF 2,