You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Sylvain Lebresne (JIRA)" <ji...@apache.org> on 2012/06/01 11:05:23 UTC
[jira] [Commented] (CASSANDRA-4264) live ratio limit 64.0 is way
too low
[ https://issues.apache.org/jira/browse/CASSANDRA-4264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13287277#comment-13287277 ]
Sylvain Lebresne commented on CASSANDRA-4264:
---------------------------------------------
The problem of changing SC.size() (4264.txt) is that SC.serializedSize() reuse it, so this will break serialization. Attaching a v2 that just make SC.size() and SC.serializedSize() return the same value (as we do for Column). This pretty much make having both size() and serializedSize() in IColumn useless, but 1.2 cleans that up anyway, so I'd suggest not getting too fancy here.
> live ratio limit 64.0 is way too low
> ------------------------------------
>
> Key: CASSANDRA-4264
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4264
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Affects Versions: 0.8.0
> Environment: FreeBSD 8 - 64 bit
> Reporter: Radim Kolar
> Assignee: Jonathan Ellis
> Priority: Trivial
> Fix For: 1.1.1
>
> Attachments: 4264-v2.txt, 4264.txt, patch-liveratio.txt
>
>
> Currently live ratio is limited to 64.0. This is way too low.
> WARN [MemoryMeter:1] Memtable.java (line 181) setting live ratio to maximum of 64 instead of xxxx
> values seen in log are ofter larger than 64.0 limit. I propose to use 100.0 as new limit.
> ponto:(admin)log/cassandra>grep "to maximum of 64" system.log.1
> WARN [MemoryMeter:1] 2012-02-03 00:00:19,444 Memtable.java (line 181) setting live ratio to maximum of 64 instead of 64.9096047648211
> WARN [MemoryMeter:1] 2012-02-08 00:00:17,379 Memtable.java (line 181) setting live ratio to maximum of 64 instead of 68.81016452376322
> WARN [MemoryMeter:1] 2012-02-08 00:00:32,358 Memtable.java (line 181) setting live ratio to maximum of 64 instead of 88.49747308025415
> WARN [MemoryMeter:1] 2012-02-09 00:00:08,448 Memtable.java (line 181) setting live ratio to maximum of 64 instead of 76.2444888765154
> WARN [MemoryMeter:1] 2012-02-10 18:18:52,677 Memtable.java (line 181) setting live ratio to maximum of 64 instead of 142.22477982642255
> WARN [MemoryMeter:1] 2012-02-20 00:00:53,753 Memtable.java (line 181) setting live ratio to maximum of 64 instead of 88.19832386767173
> WARN [MemoryMeter:1] 2012-03-02 10:41:00,232 Memtable.java (line 181) setting live ratio to maximum of 64 instead of 419.9607495592804
> WARN [MemoryMeter:1] 2012-03-07 14:13:15,141 Memtable.java (line 181) setting live ratio to maximum of 64 instead of Infinity
> WARN [MemoryMeter:1] 2012-03-08 00:01:12,766 Memtable.java (line 181) setting live ratio to maximum of 64 instead of 94.20215772717702
> WARN [MemoryMeter:1] 2012-03-09 00:00:38,633 Memtable.java (line 181) setting live ratio to maximum of 64 instead of 98.54003447121715
> WARN [MemoryMeter:1] 2012-03-11 00:00:13,243 Memtable.java (line 181) setting live ratio to maximum of 64 instead of 193.14262214179965
> WARN [MemoryMeter:1] 2012-03-14 00:00:26,709 Memtable.java (line 181) setting live ratio to maximum of 64 instead of 103.88360138951437
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira