Hi,
Depends on how much latency can your app tolerate. You always want to make
sure that client side timeouts are set greater than server side timeout
value. So that client is n't timing out while server is still serving the
requests.
You might want to start with defaults and try bumping up. So
Hi Christian,
You can do host replacement host by host keeping the replace args of the
old node.
https://docs.datastax.com/en/cassandra/3.0/cassandra/operations/opsReplaceLiveNode.html
- Anil
On Fri, Jun 15, 2018 at 12:43 AM, Christian Lorenz <
christian.lor...@webtrekk.com> wrote:
> Hi Rahul,
There are no bad GCs in the gclog (worse is like 100ms). Everything looks great
actually from what I see. CPU utilization isn't inherently a bad thing for what
its worth.
Chris
> On Jun 14, 2018, at 1:18 PM, rajpal reddy wrote:
>
> Hey Chris,
>
> Sorry to bother you. Did you get a chance to
Do you have an actual performance issue anywhere at the application level?
If not, I wouldn't spend too much time on it - load avg is a sort of odd
indirect metric that may or may not mean anything depending on the
situation.
On Fri, Jun 15, 2018 at 6:49 AM, Igor Leão wrote:
> Hi there,
>
> I ha
Hi there,
I have a Cassandra cluster running on Kubernetes. This cluster has 8
running instances with 8Gb of memory and 5 CPU cores. I can see a high load
avg in multiple instances, but no IO wait and moderate CPU usage.
Do you know how I can solve this issue?
Best,
Igor
Good time of day everyone,
I've got a question on timeouts setting practice.
I've got a 4-node cluster with only a handful of users, constant data
inserts and very large partitions (up to 450+mb, which is 4 times larger
than general cassandra manuals recommend). Data is held on hdd.
What are gen
Good time of day everyone,
I've got three questions on Cassandra paging mechanics and cluster usage
regulation.
1) Am I correct to assume that the larger page size some user session has
set - the larger portion of cluster/coordinator node resources will be
hogged by the corresponding session?
2)
Hi Rahul,
thanks for your suggestions. The Node size is ~600 GB, cluster size ~4,5 TB.
There is no strict time limitation as long as the data move can be done while
the application is still online.
Do you have any gut feeling how long a dc-sync of this cluster size would take?
Regards,
Christia
