, 'DC1': '3', 'DC2': '3', 'DC3': '3'};
>
> You may see similar problem for other system keyspaces. Do the same thing.
>
> Cheers,
>
> Yabin
>
> On Thu, Sep 22, 2016 at 1:44 PM, Timo Ahokas
> wrote:
>
>
e the system_distributed keyspace to
match this?
-Timo
On 22 September 2016 at 19:23, Timo Ahokas wrote:
> Hi Alain,
>
> Thanks a lot for a helping out!
>
> Some of the basic keyspace / cluster info you requested:
>
> # echo "DESCRIBE KEYSPACE system_d
# echo "DESCRIBE KEYSPACE system_distributed;" |
> cqlsh $(hostname -I | awk '{print $1}')
>
> CREATE KEYSPACE system_distributed WITH replication = {'class':
> 'SimpleStrategy', 'replication_factor': '3'} AND durable_writes = t
Hi,
We have a Cassandra 3.0.8 cluster (recently upgraded from 2.1.15) currently
running in two data centers (13 and 19 nodes, RF3 in both). We are adding a
third data center before decommissioning one of the earlier ones.
Installing Cassandra (3.0.8) goes fine and all the nodes join the cluster
(n
Hi Diane,
Sounds a bit like the client might be the limiting factor in your test -
not the server. Especially if you're using one single threaded client, you
might not be loading the backend in any significant way. Have you done any
vertical scaling tests (identical client, bigger server)? if the
