Re: Query on Data Modelling of a specific usecase

How much data do you plan to store in each table? I’ll be honest, this doesn’t sound like a Cassandra use case at first glance. 1 table per report x 1000 is going to be a bad time. Odds are with different queries, you’ll need multiple views, so lets call that a handful of tables per report.

Re: Exceptions when upgrade from 2.1.14 to 2.2.5

Thanks Jeff & Hannu, Yeah, that's my guess too, I walk around this by set -Dcassandra.commitlog.ignorereplayerrors=true. Before upgrade, we did run `nodetool drain`, but seems the 2.1 commit log were not cleared, and still got replayed by 2.2. Thanks Dikang. On Tue, Apr 18, 2017 at 11:09 PM,

Re: WriteTimeoutException with LWT after few milliseconds

On 2017-04-19 08:10 (-0700), Sylvain Lebresne wrote: > This is https://issues.apache.org/jira/browse/CASSANDRA-9328 and I'd rather > not repeat myself here so I'll let you read the details. Let's maybe not > open another JIRA ticket though since we have this one. >

Re: WriteTimeoutException with LWT after few milliseconds

This is https://issues.apache.org/jira/browse/CASSANDRA-9328 and I'd rather not repeat myself here so I'll let you read the details. Let's maybe not open another JIRA ticket though since we have this one. On Wed, Apr 19, 2017 at 4:29 PM, benjamin roth wrote: > Thanks, Jeff! >

Re: WriteTimeoutException with LWT after few milliseconds

Thanks, Jeff! As soon as I have some spare time I will try to reproduce and open a Jira for it. 2017-04-19 16:27 GMT+02:00 Jeff Jirsa : > > > On 2017-04-13 05:13 (-0700), benjamin roth wrote: > > I found out that if the WTEs occur, there was already another

Re: WriteTimeoutException with LWT after few milliseconds

On 2017-04-13 05:13 (-0700), benjamin roth wrote: > I found out that if the WTEs occur, there was already another process > inserting the same primary key because I found duplicates in some places > that perfectly match the WTE logs. > > Does anybody know, why this throws a

AW: Cassandra Client very CPU intensive

Ah, by the way - we are using Cassandra 3.10 and the spark connector version 2.0.0

Cassandra Client very CPU intensive

We are using Spark to do aggregations of our Cassandra data. We recognized even quite simple jobs to be way to slow and narrowed it down to the data fetching from C*. It would not be surprising that the most of the time is spend on fetching the data. But actually for a query (using the

Re: Query on Data Modelling of a specific usecase

Looking for cassandra expert's recommendation on above usecase, please reply. On Mon, Apr 17, 2017 at 7:37 PM, Naresh Yadav wrote: > Hi all, > > This is my existing table configured on apache-cassandra-3.0.9: > > CREATE TABLE report_id1 ( >mc_id text, >tag_id text,

Re: Multiple nodes decommission

On 2017-04-12 11:30 (-0700), Vlad wrote: > Interesting, there is no such explicit warning for v.3 > https://docs.datastax.com/en/cassandra/3.0/cassandra/operations/opsAddNodeToCluster.html > It says >- Start the bootstrap node. >- verify that the node is fully

Re: Exceptions when upgrade from 2.1.14 to 2.2.5

On 2017-04-18 18:57 (-0700), Dikang Gu wrote: > Hello there, > > We are upgrading one of our cluster from 2.1.14 to 2.2.5, but cassandra had > problems replaying the commit logs... > > Here is the exception, does anyone experience similar before? > >