Sorry, I forgot to mention. I am running 0.6.6
On 3/6/11 3:27 PM, Aaron Morton wrote:
Under 0.6 am not sure off the top of my head. Would need to dig into
it, its probably been discussed here though.
Check the row size and let us know what version you are using first.
Aaron
On 7/03/2011, at
Under 0.6 am not sure off the top of my head. Would need to dig into it, its
probably been discussed here though.
Check the row size and let us know what version you are using first.
Aaron
On 7/03/2011, at 5:50 AM, Mark wrote:
> If its determined that this is due to a very large row, what are
If its determined that this is due to a very large row, what are my options?
Thanks
On 3/5/11 7:11 PM, aaron morton wrote:
First question is which version are you running ? Am guessing 0.6
something
If you have OOM in the compaction thread it may be because of a very
large row. The CF inform
First question is which version are you running ? Am guessing 0.6 something
If you have OOM in the compaction thread it may be because of a very large row.
The CF information available through JConsole will give you the max row size
for the CF.
Your setting for RowWarningThresholdInMB is 512, h
Thats very nice of you. Thanks
MyCluster
true
true
128
org.apache.cassandra.locator.RackUnawareStrategy
2
org.apache.cassandra.locator.EndPointSnitch
org.apache.cassandra.auth.AllowAllAuthenticator
org.apache.cassandra.dht.RandomPartitioner
/var/lib/cassandra/saved_caches
/var/li
I have been through tuning for GC and OOM recently. If you can provide the
cassandra.yaml, I can help. Mostly I had to play with memtable thresholds.
Thanks,
Naren
On Fri, Mar 4, 2011 at 12:43 PM, Mark wrote:
> We have 7 column families and we are not using the default key cache
> (20).
>
>
We have 7 column families and we are not using the default key cache
(20).
These were our initial settings so it was not in response to anything.
Would you recommend anything else? Thanks
On 3/4/11 12:34 PM, Chris Burroughs wrote:
- Are you using a key cache? How many keys do you have?
- Are you using a key cache? How many keys do you have? Across how
many column families
You configuration is unusual both in terms of not setting min heap ==
max heap and the percentage of available RAM used for the heap. Did you
change the heap size in response to errors or for another reason?
See also:
http://www.datastax.com/docs/0.7/troubleshooting/index#nodes-are-dying-with-oom-errors
On 03/04/2011 03:05 PM, Chris Burroughs wrote:
> - Does this occur only during compaction or at seemingly random times?
> - How large is your heap? What jvm settings are you using? How much
> physical
- Does this occur only during compaction or at seemingly random times?
- How large is your heap? What jvm settings are you using? How much
physical RAM do you have?
- Do you have the row and/or key cache enabled? How are they
configured? How large are they when the OOM is thrown?
On 03/04/2011
10 matches
Mail list logo