cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <>
Subject [jira] Resolved: (CASSANDRA-1461) Make rows_cached and keys_cached globally override-able
Date Fri, 03 Sep 2010 20:32:33 GMT


Jonathan Ellis resolved CASSANDRA-1461.

    Resolution: Not A Problem

let's keep it simple.  cache sizing is something that is easily scriptable w/ nodetool or
other solutions should the need arise.  let's not introduce an extra layer of complexity.

> Make rows_cached and keys_cached globally override-able
> -------------------------------------------------------
>                 Key: CASSANDRA-1461
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Jeremy Hanna
>            Assignee: Jeremy Hanna
> It would be nice to make rows_cached and keys_cached globally override-able.
> rows_cached - options to disable globally
> It would be nice to have a setting to be able to globally disable the rows_cached setting.
 In a system where there are multiple users/applications on a single cassandra cluster, rows_cached
can become unmanageable in its current form.  It's just too memory intensive and with competing
applications on a single cluster, it's hard to guarantee isolation and QoS.
> keys_cached - option to have a global limit override
> When there are multiple users/application, even the keys_cached could potentially get
out of control.  So it would be nice to be able give an overall limit on how many keys can
be cached per column family or possibly a total for the keyspace, as keyspace usually translates
into a specific application.  So once the column family has reached the global limit, it would
just stay at that limit.

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

View raw message