[jira] [Updated] (CASSANDRA-2698) Instrument repair to be able to assess it's efficiency (precision)

[ https://issues.apache.org/jira/browse/CASSANDRA-2698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benedict updated CASSANDRA-2698: Attachment: patch.diff Instrument repair to be able to assess it's efficiency (precision)

[jira] [Commented] (CASSANDRA-2698) Instrument repair to be able to assess it's efficiency (precision)

[ https://issues.apache.org/jira/browse/CASSANDRA-2698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13609625#comment-13609625 ] Benedict commented on CASSANDRA-2698: - Hi, I've uploaded a patch for this issue

[jira] [Updated] (CASSANDRA-2698) Instrument repair to be able to assess it's efficiency (precision)

[ https://issues.apache.org/jira/browse/CASSANDRA-2698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benedict updated CASSANDRA-2698: Attachment: patch-rebased.diff Instrument repair to be able to assess it's efficiency

[jira] [Commented] (CASSANDRA-2698) Instrument repair to be able to assess it's efficiency (precision)

[ https://issues.apache.org/jira/browse/CASSANDRA-2698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13616569#comment-13616569 ] Benedict commented on CASSANDRA-2698: - Hi Yuki, The patch was created some time

[jira] [Comment Edited] (CASSANDRA-2698) Instrument repair to be able to assess it's efficiency (precision)

[ https://issues.apache.org/jira/browse/CASSANDRA-2698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13616569#comment-13616569 ] Benedict edited comment on CASSANDRA-2698 at 3/28/13 8:26 PM:

[jira] [Commented] (CASSANDRA-2698) Instrument repair to be able to assess it's efficiency (precision)

[ https://issues.apache.org/jira/browse/CASSANDRA-2698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13626520#comment-13626520 ] Benedict commented on CASSANDRA-2698: - Hi Yuki, Without in some way collecting

[jira] [Commented] (CASSANDRA-7631) Allow Stress to write directly to SSTables

[ https://issues.apache.org/jira/browse/CASSANDRA-7631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14080759#comment-14080759 ] Benedict commented on CASSANDRA-7631: - Feel free to leave this one for me, as I'll

[jira] [Commented] (CASSANDRA-7593) Errors when upgrading through several versions to 2.1

[ https://issues.apache.org/jira/browse/CASSANDRA-7593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14080825#comment-14080825 ] Benedict commented on CASSANDRA-7593: - Might be better to just expose this in

[jira] [Commented] (CASSANDRA-7567) when the commit_log disk for a single node is overwhelmed the entire cluster slows down

[ https://issues.apache.org/jira/browse/CASSANDRA-7567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14081045#comment-14081045 ] Benedict commented on CASSANDRA-7567: - Which mode of connectivity? smart thrift

[jira] [Commented] (CASSANDRA-7567) when the commit_log disk for a single node is overwhelmed the entire cluster slows down

[ https://issues.apache.org/jira/browse/CASSANDRA-7567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14081060#comment-14081060 ] Benedict commented on CASSANDRA-7567: - So Java driver then (cql3 native prepared

[jira] [Updated] (CASSANDRA-7658) stress connects to all nodes when it shouldn't

[ https://issues.apache.org/jira/browse/CASSANDRA-7658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benedict updated CASSANDRA-7658: Issue Type: Improvement (was: Bug) stress connects to all nodes when it shouldn't

[jira] [Updated] (CASSANDRA-7658) stress connects to all nodes when it shouldn't

[ https://issues.apache.org/jira/browse/CASSANDRA-7658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benedict updated CASSANDRA-7658: Priority: Minor (was: Major) stress connects to all nodes when it shouldn't

[jira] [Commented] (CASSANDRA-7658) stress connects to all nodes when it shouldn't

[ https://issues.apache.org/jira/browse/CASSANDRA-7658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14081063#comment-14081063 ] Benedict commented on CASSANDRA-7658: - You're inferring a property of the 'node'

[jira] [Commented] (CASSANDRA-7658) stress connects to all nodes when it shouldn't

[ https://issues.apache.org/jira/browse/CASSANDRA-7658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14081071#comment-14081071 ] Benedict commented on CASSANDRA-7658: - old-stress has no distinction between a

[jira] [Assigned] (CASSANDRA-7631) Allow Stress to write directly to SSTables

[ https://issues.apache.org/jira/browse/CASSANDRA-7631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benedict reassigned CASSANDRA-7631: --- Assignee: Benedict (was: Russell Alexander Spitzer) Allow Stress to write directly to

[jira] [Updated] (CASSANDRA-7631) Allow Stress to write directly to SSTables

[ https://issues.apache.org/jira/browse/CASSANDRA-7631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benedict updated CASSANDRA-7631: Assignee: Russell Alexander Spitzer (was: Benedict) Allow Stress to write directly to

[jira] [Commented] (CASSANDRA-7631) Allow Stress to write directly to SSTables

[ https://issues.apache.org/jira/browse/CASSANDRA-7631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14081116#comment-14081116 ] Benedict commented on CASSANDRA-7631: - Ok, in that case some various random

[jira] [Commented] (CASSANDRA-7644) tracing does not log commitlog/memtable ops when the coordinator is a replica

[ https://issues.apache.org/jira/browse/CASSANDRA-7644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14081129#comment-14081129 ] Benedict commented on CASSANDRA-7644: - LGTM tracing does not log

[jira] [Commented] (CASSANDRA-7593) Errors when upgrading through several versions to 2.1

[ https://issues.apache.org/jira/browse/CASSANDRA-7593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14081135#comment-14081135 ] Benedict commented on CASSANDRA-7593: - Yes, this is what I meant when I said

[jira] [Commented] (CASSANDRA-7511) Always flush on TRUNCATE

[ https://issues.apache.org/jira/browse/CASSANDRA-7511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14082295#comment-14082295 ] Benedict commented on CASSANDRA-7511: - Looking at 2.1, it is actually still

[jira] [Commented] (CASSANDRA-7631) Allow Stress to write directly to SSTables

[ https://issues.apache.org/jira/browse/CASSANDRA-7631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14082854#comment-14082854 ] Benedict commented on CASSANDRA-7631: - I'd be inclined to keep this feature for

[jira] [Commented] (CASSANDRA-7631) Allow Stress to write directly to SSTables

[ https://issues.apache.org/jira/browse/CASSANDRA-7631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14082880#comment-14082880 ] Benedict commented on CASSANDRA-7631: - I think it's a bit early for that. Let's

[jira] [Commented] (CASSANDRA-6276) CQL: Map can not be created with the same name as a previously dropped list

[ https://issues.apache.org/jira/browse/CASSANDRA-6276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14084921#comment-14084921 ] Benedict commented on CASSANDRA-6276: - 3.0 storage engine won't be universal for a

[jira] [Updated] (CASSANDRA-7546) AtomicSortedColumns.addAllWithSizeDelta has a spin loop that allocates memory

[ https://issues.apache.org/jira/browse/CASSANDRA-7546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benedict updated CASSANDRA-7546: Attachment: 7546.20_6.txt I've attached a slightly tweaked version, making things a little

[jira] [Updated] (CASSANDRA-7704) FileNotFoundException during STREAM-OUT triggers 100% CPU usage

[ https://issues.apache.org/jira/browse/CASSANDRA-7704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benedict updated CASSANDRA-7704: Attachment: 7704.txt Attaching a patch that I think addresses this. There are a number of

[jira] [Assigned] (CASSANDRA-7704) FileNotFoundException during STREAM-OUT triggers 100% CPU usage

[ https://issues.apache.org/jira/browse/CASSANDRA-7704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benedict reassigned CASSANDRA-7704: --- Assignee: Benedict FileNotFoundException during STREAM-OUT triggers 100% CPU usage

[jira] [Commented] (CASSANDRA-7704) FileNotFoundException during STREAM-OUT triggers 100% CPU usage

[ https://issues.apache.org/jira/browse/CASSANDRA-7704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14087577#comment-14087577 ] Benedict commented on CASSANDRA-7704: - [~rbranson], ftr, could we get the earlier

[jira] [Created] (CASSANDRA-7705) Safer Resource Management

Benedict created CASSANDRA-7705: --- Summary: Safer Resource Management Key: CASSANDRA-7705 URL: https://issues.apache.org/jira/browse/CASSANDRA-7705 Project: Cassandra Issue Type: Improvement

[jira] [Updated] (CASSANDRA-7705) Safer Resource Management

[ https://issues.apache.org/jira/browse/CASSANDRA-7705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benedict updated CASSANDRA-7705: Description: We've had a spate of bugs recently with bad reference counting. these can have

[jira] [Commented] (CASSANDRA-7546) AtomicSortedColumns.addAllWithSizeDelta has a spin loop that allocates memory

[ https://issues.apache.org/jira/browse/CASSANDRA-7546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14087814#comment-14087814 ] Benedict commented on CASSANDRA-7546: - Well, technically we never ever call

[jira] [Comment Edited] (CASSANDRA-7546) AtomicSortedColumns.addAllWithSizeDelta has a spin loop that allocates memory

[ https://issues.apache.org/jira/browse/CASSANDRA-7546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14087814#comment-14087814 ] Benedict edited comment on CASSANDRA-7546 at 8/6/14 3:56 PM:

[jira] [Commented] (CASSANDRA-7546) AtomicSortedColumns.addAllWithSizeDelta has a spin loop that allocates memory

[ https://issues.apache.org/jira/browse/CASSANDRA-7546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14087850#comment-14087850 ] Benedict commented on CASSANDRA-7546: - bq. We probably mean to the left of...

[jira] [Commented] (CASSANDRA-7546) AtomicSortedColumns.addAllWithSizeDelta has a spin loop that allocates memory

[ https://issues.apache.org/jira/browse/CASSANDRA-7546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14087885#comment-14087885 ] Benedict commented on CASSANDRA-7546: - Sounds good, thanks!

[jira] [Commented] (CASSANDRA-7282) Faster Memtable map

[ https://issues.apache.org/jira/browse/CASSANDRA-7282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14089019#comment-14089019 ] Benedict commented on CASSANDRA-7282: - Just pushed a minor update removing an

[jira] [Commented] (CASSANDRA-7695) Inserting the same row in parallel causes bad data to be returned to the client

[ https://issues.apache.org/jira/browse/CASSANDRA-7695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14089282#comment-14089282 ] Benedict commented on CASSANDRA-7695: - LGTM. Would prefer we call the test

[jira] [Commented] (CASSANDRA-7628) Tools java driver needs to be updated

[ https://issues.apache.org/jira/browse/CASSANDRA-7628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14089959#comment-14089959 ] Benedict commented on CASSANDRA-7628: - FTR, 2.1.0-rc1 works fine dropped in as

[jira] [Commented] (CASSANDRA-7628) Tools java driver needs to be updated

[ https://issues.apache.org/jira/browse/CASSANDRA-7628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14090426#comment-14090426 ] Benedict commented on CASSANDRA-7628: - Since 2.1.0 is still rc, I'd say that's a

[jira] [Commented] (CASSANDRA-7628) Tools java driver needs to be updated

[ https://issues.apache.org/jira/browse/CASSANDRA-7628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14090557#comment-14090557 ] Benedict commented on CASSANDRA-7628: - Looks like you didn't update the tools/lib

[jira] [Commented] (CASSANDRA-7628) Tools java driver needs to be updated

[ https://issues.apache.org/jira/browse/CASSANDRA-7628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14090569#comment-14090569 ] Benedict commented on CASSANDRA-7628: - I think we had to upgrade it independently

[jira] [Commented] (CASSANDRA-7447) New sstable format with support for columnar layout

[ https://issues.apache.org/jira/browse/CASSANDRA-7447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14090655#comment-14090655 ] Benedict commented on CASSANDRA-7447: - bq. CASSANDRA-7443 is good to clean up the

[jira] [Commented] (CASSANDRA-7704) FileNotFoundException during STREAM-OUT triggers 100% CPU usage

[ https://issues.apache.org/jira/browse/CASSANDRA-7704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14091053#comment-14091053 ] Benedict commented on CASSANDRA-7704: - My mistake. I thought on IRC you said there

[jira] [Commented] (CASSANDRA-7447) New sstable format with support for columnar layout

[ https://issues.apache.org/jira/browse/CASSANDRA-7447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14091084#comment-14091084 ] Benedict commented on CASSANDRA-7447: - bq. Is there any reason why you want to put

[jira] [Commented] (CASSANDRA-7447) New sstable format with support for columnar layout

[ https://issues.apache.org/jira/browse/CASSANDRA-7447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14091220#comment-14091220 ] Benedict commented on CASSANDRA-7447: - bq. you already have all the code in place

[jira] [Created] (CASSANDRA-7735) Remove ref-counting of netty buffers

Benedict created CASSANDRA-7735: --- Summary: Remove ref-counting of netty buffers Key: CASSANDRA-7735 URL: https://issues.apache.org/jira/browse/CASSANDRA-7735 Project: Cassandra Issue Type: Bug

[jira] [Created] (CASSANDRA-7736) Clean-up, justify (and reduce) each use of @Inline

Benedict created CASSANDRA-7736: --- Summary: Clean-up, justify (and reduce) each use of @Inline Key: CASSANDRA-7736 URL: https://issues.apache.org/jira/browse/CASSANDRA-7736 Project: Cassandra

[jira] [Commented] (CASSANDRA-7736) Clean-up, justify (and reduce) each use of @Inline

[ https://issues.apache.org/jira/browse/CASSANDRA-7736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14092484#comment-14092484 ] Benedict commented on CASSANDRA-7736: - Thanks. In general inlining is unlikely

[jira] [Created] (CASSANDRA-7738) Permit CL overuse to be explicitly bounded

Benedict created CASSANDRA-7738: --- Summary: Permit CL overuse to be explicitly bounded Key: CASSANDRA-7738 URL: https://issues.apache.org/jira/browse/CASSANDRA-7738 Project: Cassandra Issue

[jira] [Commented] (CASSANDRA-7743) Possible C* OOM issue during long running test

[ https://issues.apache.org/jira/browse/CASSANDRA-7743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14093206#comment-14093206 ] Benedict commented on CASSANDRA-7743: - Are you running with

[jira] [Resolved] (CASSANDRA-7732) Counter replication mutation can have corrupt cell name values (via pooled Netty buffers)

[ https://issues.apache.org/jira/browse/CASSANDRA-7732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benedict resolved CASSANDRA-7732. - Resolution: Not a Problem Closing as we're removing ref-counting for 2.1 until we can come

[jira] [Commented] (CASSANDRA-7735) Remove ref-counting of netty buffers

[ https://issues.apache.org/jira/browse/CASSANDRA-7735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14093323#comment-14093323 ] Benedict commented on CASSANDRA-7735: - Yes. Linked/closed CASSANDRA-7732. Remove

[jira] [Commented] (CASSANDRA-7732) Counter replication mutation can have corrupt cell name values (via pooled Netty buffers)

[ https://issues.apache.org/jira/browse/CASSANDRA-7732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14093348#comment-14093348 ] Benedict commented on CASSANDRA-7732: - Yes, see the linked (superceded-by) issue,

[jira] [Commented] (CASSANDRA-7704) FileNotFoundException during STREAM-OUT triggers 100% CPU usage

[ https://issues.apache.org/jira/browse/CASSANDRA-7704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14093450#comment-14093450 ] Benedict commented on CASSANDRA-7704: - [~yukim] was that comment a +1 on the 2.0

[jira] [Updated] (CASSANDRA-7704) FileNotFoundException during STREAM-OUT triggers 100% CPU usage

[ https://issues.apache.org/jira/browse/CASSANDRA-7704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benedict updated CASSANDRA-7704: Attachment: 7704.20.v2.txt FTR, there was a (probably innocuous) mistake in that patch; fixed

[jira] [Commented] (CASSANDRA-7735) Remove ref-counting of netty buffers

[ https://issues.apache.org/jira/browse/CASSANDRA-7735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14093476#comment-14093476 ] Benedict commented on CASSANDRA-7735: - LGTM. nit: BatchStatement,

[jira] [Commented] (CASSANDRA-7728) ConcurrentModificationException after upgrade to trunk

[ https://issues.apache.org/jira/browse/CASSANDRA-7728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14093499#comment-14093499 ] Benedict commented on CASSANDRA-7728: - Looks related to CASSANDRA-7116 - looks

[jira] [Commented] (CASSANDRA-7743) Possible C* OOM issue during long running test

[ https://issues.apache.org/jira/browse/CASSANDRA-7743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14093976#comment-14093976 ] Benedict commented on CASSANDRA-7743: - Could we get some heap dumps? Sounds to me

[jira] [Commented] (CASSANDRA-7750) Do not flush on truncate if durable_writes is false.

[ https://issues.apache.org/jira/browse/CASSANDRA-7750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14094071#comment-14094071 ] Benedict commented on CASSANDRA-7750: - I'd rather we did not reintroduce the

[jira] [Commented] (CASSANDRA-7743) Possible C* OOM issue during long running test

[ https://issues.apache.org/jira/browse/CASSANDRA-7743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14095411#comment-14095411 ] Benedict commented on CASSANDRA-7743: - No, but I don't think it's likely to be

[jira] [Commented] (CASSANDRA-7743) Possible C* OOM issue during long running test

[ https://issues.apache.org/jira/browse/CASSANDRA-7743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14095780#comment-14095780 ] Benedict commented on CASSANDRA-7743: - It looks like the problem is caused by a

[jira] [Assigned] (CASSANDRA-7743) Possible C* OOM issue during long running test

[ https://issues.apache.org/jira/browse/CASSANDRA-7743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benedict reassigned CASSANDRA-7743: --- Assignee: Benedict Possible C* OOM issue during long running test

[jira] [Commented] (CASSANDRA-7743) Possible C* OOM issue during long running test

[ https://issues.apache.org/jira/browse/CASSANDRA-7743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14096619#comment-14096619 ] Benedict commented on CASSANDRA-7743: - Hmm. So, looking at this a little more

[jira] [Commented] (CASSANDRA-7743) Possible C* OOM issue during long running test

[ https://issues.apache.org/jira/browse/CASSANDRA-7743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14096631#comment-14096631 ] Benedict commented on CASSANDRA-7743: - I haven't got to that stage yet, I'm just

[jira] [Commented] (CASSANDRA-7743) Possible C* OOM issue during long running test

[ https://issues.apache.org/jira/browse/CASSANDRA-7743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14096638#comment-14096638 ] Benedict commented on CASSANDRA-7743: - We're conflating two pools maybe :) I mean

[jira] [Commented] (CASSANDRA-7743) Possible C* OOM issue during long running test

[ https://issues.apache.org/jira/browse/CASSANDRA-7743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14096651#comment-14096651 ] Benedict commented on CASSANDRA-7743: - bq. well it will be released after a while

[jira] [Commented] (CASSANDRA-7704) FileNotFoundException during STREAM-OUT triggers 100% CPU usage

[ https://issues.apache.org/jira/browse/CASSANDRA-7704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14096779#comment-14096779 ] Benedict commented on CASSANDRA-7704: - Not cleaning up resources is really not

[jira] [Updated] (CASSANDRA-6726) Recycle CompressedRandomAccessReader/RandomAccessReader buffers independently of their owners, and move them off-heap when possible

[ https://issues.apache.org/jira/browse/CASSANDRA-6726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benedict updated CASSANDRA-6726: Assignee: Branimir Lambov Recycle CompressedRandomAccessReader/RandomAccessReader buffers

[jira] [Updated] (CASSANDRA-5902) Dealing with hints after a topology change

[ https://issues.apache.org/jira/browse/CASSANDRA-5902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benedict updated CASSANDRA-5902: Assignee: Branimir Lambov Dealing with hints after a topology change

[jira] [Updated] (CASSANDRA-7039) DirectByteBuffer compatible LZ4 methods

[ https://issues.apache.org/jira/browse/CASSANDRA-7039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benedict updated CASSANDRA-7039: Assignee: Branimir Lambov (was: Lyuben Todorov) DirectByteBuffer compatible LZ4 methods

[jira] [Updated] (CASSANDRA-7546) AtomicSortedColumns.addAllWithSizeDelta has a spin loop that allocates memory

[ https://issues.apache.org/jira/browse/CASSANDRA-7546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benedict updated CASSANDRA-7546: Fix Version/s: 2.1.1 2.0.11 AtomicSortedColumns.addAllWithSizeDelta has a

[jira] [Updated] (CASSANDRA-7561) On DROP we should invalidate CounterKeyCache as well as Key/Row cache

[ https://issues.apache.org/jira/browse/CASSANDRA-7561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benedict updated CASSANDRA-7561: Fix Version/s: 2.1.0 On DROP we should invalidate CounterKeyCache as well as Key/Row cache

[jira] [Updated] (CASSANDRA-7704) FileNotFoundException during STREAM-OUT triggers 100% CPU usage

[ https://issues.apache.org/jira/browse/CASSANDRA-7704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benedict updated CASSANDRA-7704: Fix Version/s: 2.1.0 2.0.10 FileNotFoundException during STREAM-OUT

[jira] [Updated] (CASSANDRA-3852) use LIFO queueing policy when queue size exceeds thresholds

[ https://issues.apache.org/jira/browse/CASSANDRA-3852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benedict updated CASSANDRA-3852: Fix Version/s: 3.0 use LIFO queueing policy when queue size exceeds thresholds

[jira] [Commented] (CASSANDRA-7542) Reduce CAS contention

[ https://issues.apache.org/jira/browse/CASSANDRA-7542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14096805#comment-14096805 ] Benedict commented on CASSANDRA-7542: - [~kohlisankalp] any news? Reduce CAS

[jira] [Resolved] (CASSANDRA-6780) Memtable OffHeap GC Statistics

[ https://issues.apache.org/jira/browse/CASSANDRA-6780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benedict resolved CASSANDRA-6780. - Resolution: Later Since offheap GC has been postponed indefinitely, this ticket should also

[jira] [Resolved] (CASSANDRA-6709) Changes to KeyCache

[ https://issues.apache.org/jira/browse/CASSANDRA-6709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benedict resolved CASSANDRA-6709. - Resolution: Later Closing as the new sstable format most likely makes this unnecessary by

[jira] [Resolved] (CASSANDRA-6802) Row cache improvements

[ https://issues.apache.org/jira/browse/CASSANDRA-6802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benedict resolved CASSANDRA-6802. - Resolution: Later Since offheap GC has been postponed indefinitely, this ticket should also

[jira] [Resolved] (CASSANDRA-5019) Still too much object allocation on reads

[ https://issues.apache.org/jira/browse/CASSANDRA-5019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benedict resolved CASSANDRA-5019. - Resolution: Duplicate Since the read path will be rewritten as part of efforts to introduce

[jira] [Commented] (CASSANDRA-7029) Investigate alternative transport protocols for both client and inter-server communications

[ https://issues.apache.org/jira/browse/CASSANDRA-7029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14096817#comment-14096817 ] Benedict commented on CASSANDRA-7029: - mTCP is not stable enough, nor universal

[jira] [Commented] (CASSANDRA-7542) Reduce CAS contention

[ https://issues.apache.org/jira/browse/CASSANDRA-7542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14098326#comment-14098326 ] Benedict commented on CASSANDRA-7542: - OK. Not sure if it is worth our pursuing

[jira] [Updated] (CASSANDRA-7704) FileNotFoundException during STREAM-OUT triggers 100% CPU usage

[ https://issues.apache.org/jira/browse/CASSANDRA-7704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benedict updated CASSANDRA-7704: Attachment: 7704-2.1.txt Attaching a new version which does not cancel the task that was run,

[jira] [Updated] (CASSANDRA-7704) FileNotFoundException during STREAM-OUT triggers 100% CPU usage

[ https://issues.apache.org/jira/browse/CASSANDRA-7704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benedict updated CASSANDRA-7704: Attachment: (was: 7704.20.v2.txt) FileNotFoundException during STREAM-OUT triggers 100%

[jira] [Commented] (CASSANDRA-7763) cql_tests static_with_empty_clustering test failure

[ https://issues.apache.org/jira/browse/CASSANDRA-7763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14098406#comment-14098406 ] Benedict commented on CASSANDRA-7763: - It's a shame we've spot this now, as it's a

[jira] [Commented] (CASSANDRA-7561) On DROP we should invalidate CounterKeyCache as well as Key/Row cache

[ https://issues.apache.org/jira/browse/CASSANDRA-7561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14098811#comment-14098811 ] Benedict commented on CASSANDRA-7561: - bq. Well. It shouldn't be throwing any

[jira] [Comment Edited] (CASSANDRA-7561) On DROP we should invalidate CounterKeyCache as well as Key/Row cache

[ https://issues.apache.org/jira/browse/CASSANDRA-7561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14098811#comment-14098811 ] Benedict edited comment on CASSANDRA-7561 at 8/15/14 5:46 PM:

[jira] [Commented] (CASSANDRA-7561) On DROP we should invalidate CounterKeyCache as well as Key/Row cache

[ https://issues.apache.org/jira/browse/CASSANDRA-7561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14098858#comment-14098858 ] Benedict commented on CASSANDRA-7561: - Since this is holding up 2.1-rc6, I'm

[jira] [Created] (CASSANDRA-7784) DROP table leaves the counter and row cache in a temporarily inconsistent state that, if saved during, will cause an exception to be thrown

Benedict created CASSANDRA-7784: --- Summary: DROP table leaves the counter and row cache in a temporarily inconsistent state that, if saved during, will cause an exception to be thrown Key: CASSANDRA-7784 URL:

[jira] [Reopened] (CASSANDRA-7743) Possible C* OOM issue during long running test

[ https://issues.apache.org/jira/browse/CASSANDRA-7743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benedict reopened CASSANDRA-7743: - Tester: Pierre Laporte I'd like to get confirmation this bug is fixed before resolving

[jira] [Updated] (CASSANDRA-6809) Compressed Commit Log

[ https://issues.apache.org/jira/browse/CASSANDRA-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benedict updated CASSANDRA-6809: Assignee: Branimir Lambov Compressed Commit Log - Key:

[jira] [Updated] (CASSANDRA-6572) Workload recording / playback

[ https://issues.apache.org/jira/browse/CASSANDRA-6572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benedict updated CASSANDRA-6572: Assignee: (was: Lyuben Todorov) Workload recording / playback

[jira] [Commented] (CASSANDRA-7468) Add time-based execution to cassandra-stress

[ https://issues.apache.org/jira/browse/CASSANDRA-7468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14099525#comment-14099525 ] Benedict commented on CASSANDRA-7468: - FTR, I'm planning to address this once

[jira] [Commented] (CASSANDRA-7232) Enable live replay of commit logs

[ https://issues.apache.org/jira/browse/CASSANDRA-7232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14099524#comment-14099524 ] Benedict commented on CASSANDRA-7232: - Missed this due to status != Patch

[jira] [Comment Edited] (CASSANDRA-7468) Add time-based execution to cassandra-stress

[ https://issues.apache.org/jira/browse/CASSANDRA-7468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14099525#comment-14099525 ] Benedict edited comment on CASSANDRA-7468 at 8/16/14 6:31 AM:

[jira] [Commented] (CASSANDRA-7704) FileNotFoundException during STREAM-OUT triggers 100% CPU usage

[ https://issues.apache.org/jira/browse/CASSANDRA-7704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14099527#comment-14099527 ] Benedict commented on CASSANDRA-7704: - Committed to 2.0, 2.1.0 and 2.1 branches. I

[jira] [Resolved] (CASSANDRA-7754) FileNotFoundException in MemtableFlushWriter

[ https://issues.apache.org/jira/browse/CASSANDRA-7754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benedict resolved CASSANDRA-7754. - Resolution: Not a Problem [~shalupov] the first exception you posted is occurring during

[jira] [Commented] (CASSANDRA-7743) Possible C* OOM issue during long running test

[ https://issues.apache.org/jira/browse/CASSANDRA-7743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14100197#comment-14100197 ] Benedict commented on CASSANDRA-7743: - Did you see the actual error, or have more

[jira] [Commented] (CASSANDRA-7519) Further stress improvements to generate more realistic workloads

[ https://issues.apache.org/jira/browse/CASSANDRA-7519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14100237#comment-14100237 ] Benedict commented on CASSANDRA-7519: - bq. I plan to run some test workloads to

[jira] [Commented] (CASSANDRA-7705) Safer Resource Management

[ https://issues.apache.org/jira/browse/CASSANDRA-7705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14100260#comment-14100260 ] Benedict commented on CASSANDRA-7705: - Linked four related tickets Safer

[jira] [Commented] (CASSANDRA-7220) Nodes hang with 100% CPU load

[ https://issues.apache.org/jira/browse/CASSANDRA-7220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14100261#comment-14100261 ] Benedict commented on CASSANDRA-7220: - Any other exceptions in the logs? Looks

[jira] [Commented] (CASSANDRA-7220) Nodes hang with 100% CPU load

[ https://issues.apache.org/jira/browse/CASSANDRA-7220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14100290#comment-14100290 ] Benedict commented on CASSANDRA-7220: - [~rarudduck] it looks like the issue that

[jira] [Commented] (CASSANDRA-7786) Cassandra is shutting down out of no apparent reason

[ https://issues.apache.org/jira/browse/CASSANDRA-7786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14100293#comment-14100293 ] Benedict commented on CASSANDRA-7786: - Are you sure you haven't somehow sent the

  1   2   3   4   5   6   7   8   9   10   >