[
https://issues.apache.org/jira/browse/CASSANDRA-7930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14132970#comment-14132970
]
Tyler Hobbs commented on CASSANDRA-7930:
----------------------------------------
I have a couple of concerns with the patch:
* Once the cache is at capacity, the log statement could be triggered very
frequently. There's no way for the driver to "unprepare" a statement.
* The "warn" level is usually reserved for "you are (likely) doing something
wrong". This could happen under normal circumstances and proper usage.
For those reasons, I would move the log statement to debug level. Other than
that, this looks good to me.
> Warn when evicting prepared statements from cache
> -------------------------------------------------
>
> Key: CASSANDRA-7930
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7930
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Robbie Strickland
> Assignee: Robbie Strickland
> Attachments: cassandra-2.1.txt
>
>
> The prepared statement cache is an LRU, with a max size of maxMemory / 256.
> There is currently no warning when statements are evicted, which could be
> problematic if the user is unaware that this is happening.
> At the very least, we should provide a JMX metric and possibly a log message
> indicating this is happening. At some point it may also be worthwhile to
> make this tunable for users with large numbers of statements.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
