[
https://issues.apache.org/jira/browse/CASSANDRA-7930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14141201#comment-14141201
]
Aleksey Yeschenko commented on CASSANDRA-7930:
----------------------------------------------
bq. We should just put that executor in it's own class, ScheduledTaskManager?
Then it won't have the init problem.
Yup. Maybe go one step further and put all of them somewhere centralized? At
least all the executors inside StorageSerive (scheduledTasks, tasks,
optionalTasks). *Maybe* other executors too (BatchlogManager, Gossipper, etc.)?
> 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
> Labels: bootcamp, jmx
> Fix For: 2.1.1
>
> Attachments: cassandra-2.0-v2.txt, cassandra-2.0-v3.txt,
> cassandra-2.0-v4.txt, cassandra-2.0-v5.txt, cassandra-2.0-v6.txt,
> cassandra-2.0.txt, 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)
