Use NetworkTopologyStrategy for single data center and add data centers later

Is it possible to use NetworkTopologyStrategy when creating a keyspace and add data centers later? I am just starting with an MVP application and I don't expect much traffic or data. Thus I have created only one data center. However, I'll like to add more data centers later if needed I notice

add javaagent MCAC (metric collector for apache cassandra) using cass-operator

I am using cass-operator (https://github.com/datastax/cass-operator) I want to add MCAC javaagent in my production system to monitor metrics (https://github.com/datastax/metric-collector-for-apache-cassandra). How can I do it? The general way is to add the agent information is to change

RE: add javaagent MCAC (metric collector for apache cassandra) using cass-operator

Just checked that JVM options could be added in example-cassdc-minimal.yaml

Re: Use NetworkTopologyStrategy for single data center and add data centers later

If you're planning to have another DC, then it's better to start to use NetworkTopologyStrategy from beginning - just specify the one DC, and when you get another, it will be simply to expand to it (see documentation:

Why the default value for reclaimPolicy is Delete and not Retain

Hi In cass-operator, the storage.yaml has reclaim policy Delete. Should it be Retain by default to avoid accidental deletion of data? thanks Sent from Mail for Windows 10

Re: Use NetworkTopologyStrategy for single data center and add data centers later

Yes, you absolutely can (and should) use NetworkTopologyStrategy with a single data center. In fact, I would argue that SimpleStrategy should almost never be used. But that's just me. Thanks, Aaron On Sat, Dec 19, 2020 at 3:21 AM Manu Chadha wrote: > Is it possible to use

Mutation dropped and Read-Repair performance issue

Hi All, We are facing problems of failure of Read-Repair stages with error Digest Mismatch and count is 300+ per day per node. At the same time, we are experiencing node is getting overloaded for a quick couple of seconds due to long GC pauses (of around 7-8 seconds). We are not running a repair