er
>> MBeans tab, start inspecting the GC metrics.
>>
>> /Jason
>>
>>
>> On Fri, Dec 6, 2013 at 11:40 PM, srmore wrote:
>>
>>>
>>>
>>>
>>> On Fri, Dec 6, 2013 at 9:32 AM, Vicky Kak wrote:
>>>
>>>> Hard t
be you have lots of write operations going on.
On Fri, Dec 6, 2013 at 10:06 PM, srmore wrote:
>
>
>
> On Fri, Dec 6, 2013 at 9:59 AM, Vicky Kak wrote:
>
>> You have passed the JVM configurations and not the cassandra
>> configurations which is in cassandra.yaml.
&
wrote:
>
>
>
> On Fri, Dec 6, 2013 at 9:32 AM, Vicky Kak wrote:
>
>> Hard to say much without knowing about the cassandra configurations.
>>
>
> The cassandra configuration is
> -Xms8G
> -Xmx8G
> -Xmn800m
> -XX:+UseParNewGC
> -XX:+UseConcMarkSweepGC
>
>>Why, can you give me a good example and the good way to configure archive
>>commit logs ?
Take a look at the cassandra code ;)
On Fri, Dec 6, 2013 at 3:34 PM, Bonnet Jonathan <
jonathan.bon...@externe.bnpparibas.com> wrote:
> Hello,
>
> I try to configure commitlog_archiving.properties to t
Hard to say much without knowing about the cassandra configurations.
Yes compactions/GC's could skipe the CPU, I had similar behavior with my
setup.
-VK
On Fri, Dec 6, 2013 at 7:40 PM, srmore wrote:
> We have a 3 node cluster running cassandra 1.2.12, they are pretty big
> machines 64G ram wit
I am not sure if you had got a chance to take a look at this
http://www.datastax.com/docs/1.1/troubleshooting/index#oom
http://www.datastax.com/docs/1.1/install/recommended_settings
Can you attach the cassandra logs and the cassandra.yaml, it should be able
to give us more details about the issue?
Out of curiosity with quick look I found you have directory name as
com.shift.undersiege
https://github.com/StartTheShift/UnderSiege/blob/master/src/main/java/com.shift.undersiege/StatsdReporter.java
You should have created the directory structure as
src/main/java/com/shift/undersiege/StatsReporte
