On Thu, Sep 27, 2018 at 2:24 AM Anup Shirolkar <
anup.shirol...@instaclustr.com> wrote:
>
> Most of the things look ok from your setup.
>
> You can enable Debug logs for repair duration.
> This will help identify if you are hitting a bug or other cause of unusual
> behaviour.
>
> Just a remote
Hi,
Most of the things look ok from your setup.
You can enable Debug logs for repair duration.
This will help identify if you are hitting a bug or other cause of unusual
behaviour.
Just a remote possibility, do you have other things running on nodes
besides Cassandra.
Do they consume additional
On Wed, Sep 26, 2018 at 1:07 PM Anup Shirolkar <
anup.shirol...@instaclustr.com> wrote:
>
> Looking at information you have provided, the increased CPU utilisation
> could be because of repair running on the node.
> Repairs are resource intensive operations.
>
> Restarting the node should have
Hi,
Looking at information you have provided, the increased CPU utilisation
could be because of repair running on the node.
Repairs are resource intensive operations.
Restarting the node should have halted repair operation getting the CPU
back to normal.
In case you regularly run repairs but
Hello,
On our production cluster of 30 Apache Cassandra 3.0.17 nodes we have
observed that only one node started to show about 2 times the CPU
utilization as compared to the rest (see screenshot): up to 30% vs. ~15% on
average for the other nodes.
This started more or less immediately after
