was more a decision based on
“I have to try something” than based on arguments ☺
From: Alain RODRIGUEZ [mailto:arodr...@gmail.com]
Sent: vrijdag 8 april 2016 12:46
To: user@cassandra.apache.org
Subject: Re: all the nost are not reacheable when running massive deletes
It looks like a complex issue
EX snpsearch_morphid ON snpaware.snpsearch (morphid);
>
>
>
> Which holds a lot of data. It is normaly a cf which needs to be readed but
> sometimes updated and deleted and I think the problem is there. I wanted to
> change the compaction strategy but that means that a compaction will
dedicated network.
From: daemeon reiydelle [mailto:daeme...@gmail.com<mailto:daeme...@gmail.com>]
Sent: maandag 4 april 2016 18:42
To: user@cassandra.apache.org<mailto:user@cassandra.apache.org>
Subject: Re: all the nost are not reacheable when running massive deletes
Network issues. Cou
Trujillo :
> Hi daemeon
>
>
>
> We have check network and it is ok, in fact the nodes are connecting
> between themselves with a dedicated network.
>
>
>
> *From:* daemeon reiydelle [mailto:daeme...@gmail.com]
> *Sent:* maandag 4 april 2016 18:42
> *To:* user@cassandr
Hi daemeon
We have check network and it is ok, in fact the nodes are connecting between
themselves with a dedicated network.
From: daemeon reiydelle [mailto:daeme...@gmail.com]
Sent: maandag 4 april 2016 18:42
To: user@cassandra.apache.org
Subject: Re: all the nost are not reacheable when
compactions are executed? If it is not I think is safe to update the
cluster.
Thanks for your comments
From: Alain RODRIGUEZ [mailto:arodr...@gmail.com]
Sent: maandag 4 april 2016 18:35
To: user@cassandra.apache.org
Subject: Re: all the nost are not reacheable when running massive deletes
Hola Paco
Network issues. Could be jumbo frames not consistent or other.
sent from my mobile
sent from my mobile
Daemeon C.M. Reiydelle
USA 415.501.0198
London +44.0.20.8144.9872
On Apr 4, 2016 5:34 AM, "Paco Trujillo" wrote:
> Hi everyone
>
>
>
> We are having problems with our cluster (7 nodes version
Hola Paco,
> the mutation stages pending column grows without stop, could be that the
> problem
> CPU (near 96%)
>
Yes, basically I think you are over using this cluster.
but two of them have high cpu load, especially the 232 because I am running
> a lot of deletes using cqlsh in that node.
Hi everyone
We are having problems with our cluster (7 nodes version 2.0.17) when running
"massive deletes" on one of the nodes (via cql command line). At the beginning
everything is fine, but after a while we start getting constant
NoHostAvailableException using the datastax driver:
Caused by
