You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2013/09/18 18:50:51 UTC
[jira] [Commented] (CASSANDRA-6056) Heavy write load exhausts heap
space
[ https://issues.apache.org/jira/browse/CASSANDRA-6056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13770953#comment-13770953 ]
Jonathan Ellis commented on CASSANDRA-6056:
-------------------------------------------
This sounds a lot like CASSANDRA-5982. You should have a look at that, especially if you're throwing large blobs around. If not, you should put some effort into describing what makes your workload special.
> Heavy write load exhausts heap space
> ------------------------------------
>
> Key: CASSANDRA-6056
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6056
> Project: Cassandra
> Issue Type: Bug
> Environment: Debian, Cassandra 2.0
> Reporter: arnaud-lb
>
> Issuing many INSERT or UPDATE queries cause cassandra to exhaust the heap space in a few minutes. It then gets stuck in full GCs, failing to recover.
> Observed with the default config from Datastax Debian packages, with a 8GB heap. Query rate is around 35K queries per second, with 16 concurrent queries.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira