.
Thanks a lot,
Mohamed.
On Fri, Mar 18, 2016 at 4:50 PM, Robert Coli wrote:
> On Thu, Mar 17, 2016 at 10:38 PM, Mohamed Lrhazi <
> mohamed.lrh...@georgetown.edu> wrote:
>
>> Would simply overriding this one jar file do it? else could you please
>> share a procedure?
&
Would simply overriding this one jar file do it? else could you please
share a procedure?
[root@avesterra-prod-1 ~]# rpm -qa| grep stax
datastax-ddc-tools-3.2.1-1.noarch
datastax-ddc-3.2.1-1.noarch
[root@avesterra-prod-1 ~]# cp /tmp/apache-cassandra-3.6-SNAPSHOT.jar
/usr/share/cassandra/apache-c
experiment :)
Thanks,
Mohamed.
On Fri, Mar 18, 2016 at 7:19 PM, Robert Coli wrote:
> On Fri, Mar 18, 2016 at 2:18 PM, Mohamed Lrhazi <
> mohamed.lrh...@georgetown.edu> wrote:
>
>> So, after doing an ant build from the latest source... how would one
>> "install&
gt;
> 2016-03-14 17:35 GMT-03:00 Mohamed Lrhazi :
>
>> Hi Paulo,
>>
>> Which metric should I watch for this ?
>>
>> [root@avesterra-prod-1 ~]# rpm -qa| grep datastax
>> datastax-ddc-3.2.1-1.noarch
>> datastax-ddc-tools-3.2.1-1.noarch
>> [root@a
could be hitting
> CASSANDRA-11344.
>
> 2016-03-12 19:43 GMT-03:00 Mohamed Lrhazi :
>
>> In my case, all nodes seem to be constantly logging messages like these:
>>
>> DEBUG [GossipStage:1] 2016-03-12 17:41:19,123 FailureDetector.java:456 -
>> Ignoring interval t
In my case, all nodes seem to be constantly logging messages like these:
DEBUG [GossipStage:1] 2016-03-12 17:41:19,123 FailureDetector.java:456 -
Ignoring interval time of 2000928319 for /10.212.18.170
What does that mean?
Thanks a lot,
Mohamed.
On Sat, Mar 12, 2016 at 5:39 PM, Mohamed Lrhazi
he
> available memory (~128GB) and just stops its process. This is a known bug ?
> *"
>
>
> On 03/13/2016 12:56 AM, Mohamed Lrhazi wrote:
>
> Hello,
>
> We installed Datastax community edition, on 8 nodes, RHEL7. We inserted
> some 7 billion rows into a pretty simpl
Hello,
We installed Datastax community edition, on 8 nodes, RHEL7. We inserted
some 7 billion rows into a pretty simple table. the inserts seem to have
completed without issues. but ever since, we find that the nodes reliably
run out of RAM after few hours, without any user activity at all. No rea
