Hi Bob ,
We did not use the reaper(yet) just trying to run tests against the new C*
v3 cluster .
The nodes keeps crashing all the time and these are the error we are
getting .
Any other ideas ?
Thanks!
Roy
On Wed, Jan 16, 2019 at 8:51 AM Bobbie Haynes wrote:
> Hi Roy,
> I don't
Hi Roy,
I don't think the Memory Leak issue is related to MAP errors .I
was also using Reaper in our cluster.I have seen Memory Leak issue (ERROR
[Reference-Reaper:1] 2019-01-14 00:03:46,469 Ref.java:224 - LEAK DETECTED)
when some of SStables got corrupted because of disk space issue
Hello, I have a table with 3m records and say 3m recs have empty string on
which an MView is built upon.
create table t
( c1 int, c2 text, primary key(c1));
create materialized view mv as select c2,c1 from t
WHEREc2 IS NOT NULL AND c1 IS NOT NULL
PRIMARY KEY (c2, c1);
There are recs
There are 2 DCs each with 3 nodes, and the RF used for writes is 2 and
reads its each_quorum. A lightweight transaction is used to ensure
consistency of updates across DCs. Now what is happening is for certain
records, hundreds (maybe thousands) of lwt updates are hitting the cluster
around same
