Re: Load discrepancy between old vs new nodes of Cassandra

2020-08-19 Thread Saijal Chauhan
keyspaces) because of > the size. Cheers! > -- Saijal Chauhan Infrastructure Systems Engineer Evive goevive.com

Re: Load discrepancy between old vs new nodes of Cassandra

2020-08-19 Thread Saijal Chauhan
wrote: > I would start by checking the replication settings on all your keyspaces. > There's a chance that you have keyspaces not replicated to DC3. FWIW it > would have to be an application keyspace (vs system keyspaces) because of > the size. Cheers! > -- Saijal Chauha

Load discrepancy between old vs new nodes of Cassandra

2020-08-17 Thread Saijal Chauhan
Hi, We are using Cassandra 3.0.13 We have the following datacenters: - DC1 with 7 Cassandra nodes with RF:3 (2 years old) - DC2 with 1 Cassandra node with RF:1 (4 years old) - DC3 with 2 Cassandra nodes with RF:2 (one-month-old) On DC2 and DC3, each node has 100% data. Seed nodes while

Re: Recreating materialized views in cassandra

2020-07-27 Thread Saijal Chauhan
ating or > deleting these materialized views? > > no, but be careful about the latency/throughput impact on the regular > workload. > > On Tue, 28 Jul 2020 at 00:02, Saijal Chauhan > wrote: > >> Hi, >> >> We are using Cassandra 3.0.13 >> We have the fol

Recreating materialized views in cassandra

2020-07-27 Thread Saijal Chauhan
Hi, We are using Cassandra 3.0.13 We have the following datacenters: - DC1 with 7 Cassandra nodes with RF:3 - DC2 with 2 Cassandra nodes with RF:2 - DC3 with 2 Cassandra nodes with RF:2 We are facing data inconsistency issues between base tables and materialized views. The only solution