Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Fri, 19 Sep 2014 20:01:34 +0000 (UTC)
From: "Aleksey Yeschenko (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12741281.1410641658000.80773.1411156894369@Atlassian.JIRA>
In-Reply-To: <JIRA.12741281.1410641658000@Atlassian.JIRA>
References: <JIRA.12741281.1410641658000@Atlassian.JIRA>
 <JIRA.12741281.1410641658111@arcas>
Subject: [jira] [Commented] (CASSANDRA-7930) Warn when evicting prepared
 statements from cache
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Aleksey Yeschenko commented on CASSANDRA-7930:
----------------------------------------------

Apparently switching from its own executor to one of SP's broke all the unit tests by messing with static initialization order. To make all the tests work, now, I switched back to a standalone executor from the v1 patch, in https://github.com/apache/cassandra/commit/488e775cc13044ac1a2b4bd9c4e5d544a4d15bae. [~benedict] If you see an easy way to use SP's here without tangling stuff, feel free commit it in-place.

> 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)