cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Lerer (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-11555) Make prepared statement cache size configurable
Date Mon, 02 May 2016 08:26:12 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-11555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15266223#comment-15266223
] 

Benjamin Lerer commented on CASSANDRA-11555:
--------------------------------------------

The configuration options should be added to the {{yaml}} file with some documentation. 
I would, personally, follow the way it has been done for {{key_cache_size_in_mb}} with the
default logic and validation in {{DatabaseDescriptor}}.
I think it is better to reject the input if it is invalid rather than overridding it silently.

> Make prepared statement cache size configurable
> -----------------------------------------------
>
>                 Key: CASSANDRA-11555
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11555
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: CQL
>            Reporter: Robert Stupp
>            Assignee: Robert Stupp
>            Priority: Minor
>             Fix For: 3.x
>
>
> The prepared statement caches in {{org.apache.cassandra.cql3.QueryProcessor}} are configured
using the formula {{Runtime.getRuntime().maxMemory() / 256}}. Sometimes applications may need
more than that. Proposal is to make that value configurable - probably also distinguish thrift
and native CQL3 queries (new applications don't need the thrift stuff).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message