rote:
>>>
>>>> AWS ubuntu 14.04 AMI ships with buggy enhanced networking driver –
>>>> depending on your instance types / hypervisor choice, you may want to
>>>> ensure you’re not seeing that bug.
>>>>
>>>>
>>>>
with buggy enhanced networking driver –
>>> depending on your instance types / hypervisor choice, you may want to
>>> ensure you’re not seeing that bug.
>>>
>>>
>>>
>>> *From: *Mike Heffner
>>> *Reply-To: *"user@cassandra.apache.org&q
y-To: *"user@cassandra.apache.org"
>> *Date: *Friday, July 1, 2016 at 1:10 PM
>> *To: *"user@cassandra.apache.org"
>> *Cc: *Peter Norton
>> *Subject: *Re: Ring connection timeouts with 2.2.6
>>
>>
>>
>> Jens,
>>
>>
>>
>>
uot;
> *Cc: *Peter Norton
> *Subject: *Re: Ring connection timeouts with 2.2.6
>
>
>
> Jens,
>
>
>
> We haven't noticed any particular large GC operations or even persistently
> high GC times.
>
>
>
> Mike
>
>
>
> On Thu, Jun 30, 2016 at
To: "user@cassandra.apache.org"
Cc: Peter Norton
Subject: Re: Ring connection timeouts with 2.2.6
Jens,
We haven't noticed any particular large GC operations or even persistently high
GC times.
Mike
On Thu, Jun 30, 2016 at 3:20 AM, Jens Rantil wrote:
Hi,
Could it be garbag
Jens,
We haven't noticed any particular large GC operations or even persistently
high GC times.
Mike
On Thu, Jun 30, 2016 at 3:20 AM, Jens Rantil wrote:
> Hi,
>
> Could it be garbage collection occurring on nodes that are more heavily
> loaded?
>
> Cheers,
> Jens
>
> Den sön 26 juni 2016 05:22
Hi,
Could it be garbage collection occurring on nodes that are more heavily
loaded?
Cheers,
Jens
Den sön 26 juni 2016 05:22Mike Heffner skrev:
> One thing to add, if we do a rolling restart of the ring the timeouts
> disappear entirely for several hours and performance returns to normal.
> It'
One thing to add, if we do a rolling restart of the ring the timeouts
disappear entirely for several hours and performance returns to normal.
It's as if something is leaking over time, but we haven't seen any
noticeable change in heap.
On Thu, Jun 23, 2016 at 10:38 AM, Mike Heffner wrote:
> Hi,
Hi,
We have a 12 node 2.2.6 ring running in AWS, single DC with RF=3, that is
sitting at <25% CPU, doing mostly writes, and not showing any particular
long GC times/pauses. By all observed metrics the ring is healthy and
performing well.
However, we are noticing a pretty consistent number of conn