gs, how long are the pauses (use something like: grep -i
>>>>>>> 'GCInspector'
>>>>>>> /var/log/cassandra/system.log) ?
>>>>>>>
>>>>>>> Something else you could check are local_writes stats to see if only
>
>>>>>>
>>>>>> Those are just things I would check, I have not a clue on what is
>>>>>> happening here, hope this will help.
>>>>>>
>>>>>> C*heers,
>>>>>> -
>>&g
t;>> The Last Pickle
>>>>> http://www.thelastpickle.com
>>>>>
>>>>> 2016-02-18 5:13 GMT+01:00 Mike Heffner <m...@librato.com>:
>>>>>
>>>>>> Jaydeep,
>>>>>>
>>>>>> No, we don't use any light we
6:44 PM, Jaydeep Chovatia <
chovatia.jayd...@gmail.com> wrote:
>>>>>>>
>>>>>>> Are you guys using light weight transactions in your write path?
>>>>>>>
>>>>>>> On Thu, Feb 11, 2016 at 12:36 AM, Fabrice Fa
>>
>>>>>> Are you guys using light weight transactions in your write path?
>>>>>>
>>>>>> On Thu, Feb 11, 2016 at 12:36 AM, Fabrice Facorat <
>>>>>> fabrice.faco...@gmail.com> wrote:
>>>>>>
>&
ike Heffner
>> Reply-To: "user@cassandra.apache.org"
>> Date: Wednesday, February 10, 2016 at 2:24 PM
>> To: "user@cassandra.apache.org"
>> Cc: Peter Norton
>> Subject: Re: Debugging write timeouts on Cassandra 2.2.5
>>
>> Paulo,
>>
>
hich don't have a lot of IO.
>>>>>>
>>>>>> Others IO may have great impact impact on your commitlog writing and
>>>>>> it may even block.
>>>>>>
>>>>>> An example of impact IO may have, even for Async writes:
>>&
>>>>> it may even block.
>>>>>
>>>>> An example of impact IO may have, even for Async writes:
>>>>>
>>>>> https://engineering.linkedin.com/blog/2016/02/eliminating-large-jvm-gc-pauses-caused-by-background-io-traffic
>>>>>
>
ff Jirsa <jeff.ji...@crowdstrike.com>
> wrote:
>>
>> What disk size are you using?
>>
>>
>>
>> From: Mike Heffner
>> Reply-To: "user@cassandra.apache.org"
>> Date: Wednesday, February 10, 2016 at 2:24 PM
>> To: &qu
T+01:00 Mike Heffner <m...@librato.com>:
>>>> > Jeff,
>>>> >
>>>> > We have both commitlog and data on a 4TB EBS with 10k IOPS.
>>>> >
>>>> > Mike
>>>> >
>>>> > On Wed, Feb 10, 2016 at 5:28 PM
Following up from our earlier post...
We have continued to do exhaustive testing and measuring of the numerous
hardware and configuration variables here. What we have uncovered is that
on identical hardware (including the configuration we run in production),
something between versions 2.0.17 and
;> >
>>> > Mike
>>> >
>>> > On Wed, Feb 10, 2016 at 5:28 PM, Jeff Jirsa <
>>> jeff.ji...@crowdstrike.com>
>>> > wrote:
>>> >>
>>> >> What disk size are you using?
>>> >>
>>> >
>
>> >> What disk size are you using?
>> >>
>> >>
>> >>
>> >> From: Mike Heffner
>> >> Reply-To: "user@cassandra.apache.org"
>> >> Date: Wednesday, February 10, 2016 at 2:24 PM
>> >> To: "user@cas
t; wrote:
> >>
> >> What disk size are you using?
> >>
> >>
> >>
> >> From: Mike Heffner
> >> Reply-To: "user@cassandra.apache.org"
> >> Date: Wednesday, February 10, 2016 at 2:24 PM
> >> To: "user@cassandra.apa
:28 PM, Jeff Jirsa <jeff.ji...@crowdstrike.com>
> wrote:
>>
>> What disk size are you using?
>>
>>
>>
>> From: Mike Heffner
>> Reply-To: "user@cassandra.apache.org"
>> Date: Wednesday, February 10, 2016 at 2:24 PM
>> To: "user@cassandr
Hi all,
We've recently embarked on a project to update our Cassandra infrastructure
running on EC2. We are long time users of 2.0.x and are testing out a move
to version 2.2.5 running on VPC with EBS. Our test setup is a 3 node, RF=3
cluster supporting a small write load (mirror of our staging
Are you using the same GC settings as the staging 2.0 cluster? If not,
could you try using the default GC settings (CMS) and see if that changes
anything? This is just a wild guess, but there were reports before of
G1-caused instabilities with small heap sizes (< 16GB - see CASSANDRA-10403
for
Paulo,
Thanks for the suggestion, we ran some tests against CMS and saw the same
timeouts. On that note though, we are going to try doubling the instance
sizes and testing with double the heap (even though current usage is low).
Mike
On Wed, Feb 10, 2016 at 3:40 PM, Paulo Motta
What disk size are you using?
From: Mike Heffner
Reply-To: "user@cassandra.apache.org"
Date: Wednesday, February 10, 2016 at 2:24 PM
To: "user@cassandra.apache.org"
Cc: Peter Norton
Subject: Re: Debugging write timeouts on Cassandra 2.2.5
Paulo,
Thanks for the sug
Wednesday, February 10, 2016 at 2:24 PM
> To: "user@cassandra.apache.org"
> Cc: Peter Norton
> Subject: Re: Debugging write timeouts on Cassandra 2.2.5
>
> Paulo,
>
> Thanks for the suggestion, we ran some tests against CMS and saw the same
> timeouts. On that not
20 matches
Mail list logo
