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

Rajanarayanan Thottuvaikkatumana commented on CASSANDRA-8231:
-------------------------------------------------------------

Looks like the issue is still persisting even after getting the latest… Here is 
my git log and I see the jamm jar file changes in there.

Rajanarayanans-MacBook-Pro:cassandra-trunk RajT$ git log --oneline
41435ef Merge branch 'cassandra-2.1' into trunk
cab2b25 Merge branch 'cassandra-2.0' into cassandra-2.1
0e3d9fc Validate size of indexed column values
065aeeb Merge branch 'trunk' of 
https://git-wip-us.apache.org/repos/asf/cassandra into trunk
35f173a Merge branch 'cassandra-2.1' of 
https://git-wip-us.apache.org/repos/asf/cassandra into cassandra-2.1
cd4f729 Merge branch 'cassandra-2.1' into trunk
528cc3d Merge branch 'cassandra-2.1' into trunk
6ae1b42 Better jamm 0.3.0 jar


The error message is same though:
[junit] Error opening zip file or JAR manifest missing : 
/Users/RajT/cassandra-source/cassandra-trunk/lib/jamm-0.3.0.jar 

Thanks
-Raj





> Wrong size of cached prepared statements
> ----------------------------------------
>
>                 Key: CASSANDRA-8231
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8231
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Jaroslav Kamenik
>            Assignee: Benjamin Lerer
>             Fix For: 2.1.3
>
>         Attachments: 8231-notes.txt, CASSANDRA-8231-V2-trunk.txt, 
> CASSANDRA-8231-V2.txt, CASSANDRA-8231.txt, Unsafes.java
>
>
> Cassandra counts memory footprint of prepared statements for caching 
> purposes. It seems, that there is problem with some statements, ie 
> SelectStatement. Even simple selects is counted as 100KB object, updates, 
> deletes etc have few hundreds or thousands bytes. Result is that cache - 
> QueryProcessor.preparedStatements  - holds just fraction of statements..
> I dig a little into the code, and it seems that problem is in jamm in class 
> MemoryMeter. It seems that if instance contains reference to class, it counts 
> size of whole class too. SelectStatement references EnumSet through 
> ResultSet.Metadata and EnumSet holds reference to Enum class...



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

Reply via email to