[jira] [Updated] (CASSANDRA-8525) Bloom Filter truePositive counter not updated on key cache hit

[ https://issues.apache.org/jira/browse/CASSANDRA-8525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-8525: --- Attachment: 0001-inc-truepositive-for-keycache-hits.patch Bloom Filter

[jira] [Commented] (CASSANDRA-8513) SSTableScanner may not acquire reference, but will still release it when closed

[ https://issues.apache.org/jira/browse/CASSANDRA-8513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14255545#comment-14255545 ] Marcus Eriksson commented on CASSANDRA-8513: [~benedict] could you explain

[jira] [Comment Edited] (CASSANDRA-8513) SSTableScanner may not acquire reference, but will still release it when closed

[ https://issues.apache.org/jira/browse/CASSANDRA-8513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14255545#comment-14255545 ] Marcus Eriksson edited comment on CASSANDRA-8513 at 12/22/14 8:37 AM:

[jira] [Commented] (CASSANDRA-8530) Query on a secondary index creates huge CPU spike + unable to trace

[ https://issues.apache.org/jira/browse/CASSANDRA-8530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14255578#comment-14255578 ] Sylvain Lebresne commented on CASSANDRA-8530: - We'll have a look, but know

[jira] [Commented] (CASSANDRA-8499) Ensure SSTableWriter cleans up properly after failure

[ https://issues.apache.org/jira/browse/CASSANDRA-8499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14255596#comment-14255596 ] Marcus Eriksson commented on CASSANDRA-8499: In general LGTM, but at least

[jira] [Commented] (CASSANDRA-8524) Cassandra stress user defined writes should populate sequentially

[ https://issues.apache.org/jira/browse/CASSANDRA-8524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14255600#comment-14255600 ] Benedict commented on CASSANDRA-8524: - I think it should only switch to sequential

[jira] [Commented] (CASSANDRA-4851) CQL3: improve support for paginating over composites

[ https://issues.apache.org/jira/browse/CASSANDRA-4851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14255660#comment-14255660 ] Pierre commented on CASSANDRA-4851: --- Is this patch included in cassandra 2.1.1 ?

[jira] [Comment Edited] (CASSANDRA-4851) CQL3: improve support for paginating over composites

[ https://issues.apache.org/jira/browse/CASSANDRA-4851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14255660#comment-14255660 ] Pierre edited comment on CASSANDRA-4851 at 12/22/14 11:55 AM:

[jira] [Commented] (CASSANDRA-4851) CQL3: improve support for paginating over composites

[ https://issues.apache.org/jira/browse/CASSANDRA-4851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14255669#comment-14255669 ] Aleksey Yeschenko commented on CASSANDRA-4851: -- Yes. CQL3: improve

[jira] [Commented] (CASSANDRA-4851) CQL3: improve support for paginating over composites

[ https://issues.apache.org/jira/browse/CASSANDRA-4851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14255676#comment-14255676 ] Pierre commented on CASSANDRA-4851: --- Hi Aleksey, I edited my posts, indeed it works

[jira] [Comment Edited] (CASSANDRA-4851) CQL3: improve support for paginating over composites

[ https://issues.apache.org/jira/browse/CASSANDRA-4851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14255676#comment-14255676 ] Pierre edited comment on CASSANDRA-4851 at 12/22/14 12:01 PM:

[jira] [Commented] (CASSANDRA-4851) CQL3: improve support for paginating over composites

[ https://issues.apache.org/jira/browse/CASSANDRA-4851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14255679#comment-14255679 ] Aleksey Yeschenko commented on CASSANDRA-4851: -- Try 2.1-HEAD

[jira] [Created] (CASSANDRA-8531) metric CommitLog.PendingTasks is always growing

Anton Lebedevich created CASSANDRA-8531: --- Summary: metric CommitLog.PendingTasks is always growing Key: CASSANDRA-8531 URL: https://issues.apache.org/jira/browse/CASSANDRA-8531 Project:

[jira] [Commented] (CASSANDRA-7168) Add repair aware consistency levels

[ https://issues.apache.org/jira/browse/CASSANDRA-7168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14255743#comment-14255743 ] T Jake Luciani commented on CASSANDRA-7168: --- The CollationController class

cassandra git commit: Cassandra stress user defined writes should populate sequentially

Repository: cassandra Updated Branches: refs/heads/cassandra-2.1 9775a9c68 - 29ff2d26f Cassandra stress user defined writes should populate sequentially Patch by tjake; reviewed by Benedict for CASSANDRA-8524 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit:

[2/2] cassandra git commit: Merge branch 'cassandra-2.1' into trunk

Merge branch 'cassandra-2.1' into trunk Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/977cbddc Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/977cbddc Diff:

[1/2] cassandra git commit: Cassandra stress user defined writes should populate sequentially

Repository: cassandra Updated Branches: refs/heads/trunk bf599fb5b - 977cbddc4 Cassandra stress user defined writes should populate sequentially Patch by tjake; reviewed by Benedict for CASSANDRA-8524 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit:

[jira] [Commented] (CASSANDRA-8464) Support direct buffer decompression for reads

[ https://issues.apache.org/jira/browse/CASSANDRA-8464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14255789#comment-14255789 ] T Jake Luciani commented on CASSANDRA-8464: --- I've updated the branch with

[jira] [Commented] (CASSANDRA-8099) Refactor and modernize the storage engine

[ https://issues.apache.org/jira/browse/CASSANDRA-8099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14255824#comment-14255824 ] Sylvain Lebresne commented on CASSANDRA-8099: - As an update on this I've

[1/3] cassandra git commit: ninja remove synchronized from MappedFileDataInput.readBytes

Repository: cassandra Updated Branches: refs/heads/cassandra-2.1 29ff2d26f - 5cff788ef refs/heads/trunk 977cbddc4 - 20ccf46f1 ninja remove synchronized from MappedFileDataInput.readBytes Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit:

[3/3] cassandra git commit: Merge branch 'cassandra-2.1' into trunk

Merge branch 'cassandra-2.1' into trunk Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/20ccf46f Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/20ccf46f Diff:

[2/3] cassandra git commit: ninja remove synchronized from MappedFileDataInput.readBytes

ninja remove synchronized from MappedFileDataInput.readBytes Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/5cff788e Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/5cff788e Diff:

[jira] [Commented] (CASSANDRA-8530) Query on a secondary index creates huge CPU spike + unable to trace

[ https://issues.apache.org/jira/browse/CASSANDRA-8530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14255884#comment-14255884 ] Pavel Baranov commented on CASSANDRA-8530: -- Providing a self-contained script

[jira] [Commented] (CASSANDRA-8530) Query on a secondary index creates huge CPU spike + unable to trace

[ https://issues.apache.org/jira/browse/CASSANDRA-8530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14255892#comment-14255892 ] Sylvain Lebresne commented on CASSANDRA-8530: - bq. 3. until recently we

[jira] [Commented] (CASSANDRA-8530) Query on a secondary index creates huge CPU spike + unable to trace

[ https://issues.apache.org/jira/browse/CASSANDRA-8530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14255898#comment-14255898 ] Pavel Baranov commented on CASSANDRA-8530: -- What I get from this is that the

[jira] [Updated] (CASSANDRA-8464) Support direct buffer decompression for reads

[ https://issues.apache.org/jira/browse/CASSANDRA-8464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] T Jake Luciani updated CASSANDRA-8464: -- Attachment: compression_direct.png Updated stress performance chart

[jira] [Updated] (CASSANDRA-8399) Reference Counter exception when dropping user type

[ https://issues.apache.org/jira/browse/CASSANDRA-8399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua McKenzie updated CASSANDRA-8399: --- Attachment: 8399_fix_empty_results.txt Good catch; the role of the readOrdering

[jira] [Commented] (CASSANDRA-8399) Reference Counter exception when dropping user type

[ https://issues.apache.org/jira/browse/CASSANDRA-8399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14256225#comment-14256225 ] Benedict commented on CASSANDRA-8399: - The real question is: why are we even

[jira] [Commented] (CASSANDRA-8457) nio MessagingService

[ https://issues.apache.org/jira/browse/CASSANDRA-8457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14256293#comment-14256293 ] Ariel Weisberg commented on CASSANDRA-8457: --- Testing on AWS with 6 client

[jira] [Commented] (CASSANDRA-8457) nio MessagingService

[ https://issues.apache.org/jira/browse/CASSANDRA-8457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14256326#comment-14256326 ] Ariel Weisberg commented on CASSANDRA-8457: --- Repeating these benchmarks,

[jira] [Comment Edited] (CASSANDRA-8457) nio MessagingService

[ https://issues.apache.org/jira/browse/CASSANDRA-8457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14256326#comment-14256326 ] Ariel Weisberg edited comment on CASSANDRA-8457 at 12/22/14 11:48 PM:

[jira] [Updated] (CASSANDRA-8518) Cassandra Query Request Size Estimator

[ https://issues.apache.org/jira/browse/CASSANDRA-8518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cheng Ren updated CASSANDRA-8518: - Priority: Major (was: Minor) Cassandra Query Request Size Estimator

[jira] [Updated] (CASSANDRA-8518) Cassandra Query Request Size Estimator

[ https://issues.apache.org/jira/browse/CASSANDRA-8518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cheng Ren updated CASSANDRA-8518: - Description: We have been suffering from cassandra node crash due to out of memory for a

[jira] [Commented] (CASSANDRA-8192) Better error logging on corrupt compressed SSTables: currently AssertionError in Memory.java

[ https://issues.apache.org/jira/browse/CASSANDRA-8192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14256721#comment-14256721 ] Marcus Eriksson commented on CASSANDRA-8192: I need to create a file like

[jira] [Updated] (CASSANDRA-8192) Better error logging on corrupt compressed SSTables: currently AssertionError in Memory.java

[ https://issues.apache.org/jira/browse/CASSANDRA-8192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-8192: --- Reviewer: Marcus Eriksson Better error logging on corrupt compressed SSTables:

[jira] [Comment Edited] (CASSANDRA-8192) Better error logging on corrupt compressed SSTables: currently AssertionError in Memory.java

[ https://issues.apache.org/jira/browse/CASSANDRA-8192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14256721#comment-14256721 ] Marcus Eriksson edited comment on CASSANDRA-8192 at 12/23/14 7:57 AM: