cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeremy Hanna (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (CASSANDRA-1445) Make keys/rows cached more safe
Date Fri, 03 Sep 2010 19:56:33 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-1445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jeremy Hanna resolved CASSANDRA-1445.
-------------------------------------

    Resolution: Won't Fix

Created CASSANDRA-1461 to specify a plan for certain situations.

> Make keys/rows cached more safe
> -------------------------------
>
>                 Key: CASSANDRA-1445
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1445
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Jeremy Hanna
>            Assignee: Jeremy Hanna
>            Priority: Minor
>
> Currently when a user sets keys/rows cached for their column families, they do at their
own risk.  If you cache too much information, you will get an OOM error on the server and
crash the server.
> This improvement would be to make that configuration safer.
> In order to accomplish this, we could add a configuration option for size of cache (for
either).  The server would be able to see how much data is expected to be cached based on
column family settings and make a best effort to cache it.  However, it would not exceed that
maximum value for the node (by some form of approximation).  Instead it would weight the different
values for caching and satisfy the expectation as best it can.  So it would potentially cache
less than was requested, but at least it would not crash the server.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message