It's best-practice to disable the default user ("cassandra" user) after
enabling password authentication on your cluster. The default user reads
with a CL.QUORUM when authenticating, while other users use CL.LOCAL_ONE.
This means it's more likely you could experience authentication issues,
even if
>
> Increasing new heap size generally helps when you're seeing a lot of
> promotion - if you're not seeing long major GCs, are you seeing a lot of
> promotion from eden to old gen?
> You don't typically set -Xmn (new heap size) when using G1GC
Nope not really
> currently using
>
>
> We're running with 128G memory and 30G heap size. Maybe it's good idea
> to increase the commitlog_total_space. On the other hand, even with 8G
> commitlog_total_space, replaying CL after restart takes more than 5
> minutes.
>
> In our case, the actual problem is it's causing lots of read
