[jira] [Commented] (CASSANDRA-7486) Compare CMS and G1 pause times

[ https://issues.apache.org/jira/browse/CASSANDRA-7486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14518707#comment-14518707 ] Rick Branson commented on CASSANDRA-7486: - I think it definitely makes sense

[jira] [Created] (CASSANDRA-9258) Range movement causes CPU performance impact

Rick Branson created CASSANDRA-9258: --- Summary: Range movement causes CPU performance impact Key: CASSANDRA-9258 URL: https://issues.apache.org/jira/browse/CASSANDRA-9258 Project: Cassandra

[jira] [Commented] (CASSANDRA-9258) Range movement causes CPU performance impact

[ https://issues.apache.org/jira/browse/CASSANDRA-9258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14518182#comment-14518182 ] Rick Branson commented on CASSANDRA-9258: - This is also an issue for large 2.0

[jira] [Created] (CASSANDRA-9244) replace_address is not topology-aware

Rick Branson created CASSANDRA-9244: --- Summary: replace_address is not topology-aware Key: CASSANDRA-9244 URL: https://issues.apache.org/jira/browse/CASSANDRA-9244 Project: Cassandra Issue

[jira] [Commented] (CASSANDRA-9244) replace_address is not topology-aware

[ https://issues.apache.org/jira/browse/CASSANDRA-9244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14512756#comment-14512756 ] Rick Branson commented on CASSANDRA-9244: - GossipingPropertyFileSnitch. The

[jira] [Resolved] (CASSANDRA-9227) Support num_tokens: 0

[ https://issues.apache.org/jira/browse/CASSANDRA-9227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick Branson resolved CASSANDRA-9227. - Resolution: Not A Problem We tested join_ring=false after 2.0.7 came out and didn't

[jira] [Updated] (CASSANDRA-9227) Support num_tokens: 0

[ https://issues.apache.org/jira/browse/CASSANDRA-9227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick Branson updated CASSANDRA-9227: Description: num_tokens: 0 would allow serving proxy traffic on non-storage machines.

[jira] [Created] (CASSANDRA-9227) Support num_tokens: 0

Rick Branson created CASSANDRA-9227: --- Summary: Support num_tokens: 0 Key: CASSANDRA-9227 URL: https://issues.apache.org/jira/browse/CASSANDRA-9227 Project: Cassandra Issue Type:

[jira] [Commented] (CASSANDRA-8835) 100% CPU spikes from disruptor thrift server

[ https://issues.apache.org/jira/browse/CASSANDRA-8835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14327993#comment-14327993 ] Rick Branson commented on CASSANDRA-8835: - also seeing this pop to the top

[jira] [Created] (CASSANDRA-8835) 100% CPU spikes from disruptor thrift server

Rick Branson created CASSANDRA-8835: --- Summary: 100% CPU spikes from disruptor thrift server Key: CASSANDRA-8835 URL: https://issues.apache.org/jira/browse/CASSANDRA-8835 Project: Cassandra

[jira] [Commented] (CASSANDRA-8463) Constant compaction under LCS

[ https://issues.apache.org/jira/browse/CASSANDRA-8463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14251110#comment-14251110 ] Rick Branson commented on CASSANDRA-8463: - Code LGTM. Constant compaction

[jira] [Commented] (CASSANDRA-8463) Constant compaction under LCS

[ https://issues.apache.org/jira/browse/CASSANDRA-8463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14248518#comment-14248518 ] Rick Branson commented on CASSANDRA-8463: - I applied that patch to one node.

[jira] [Commented] (CASSANDRA-8463) Constant compaction under LCS

[ https://issues.apache.org/jira/browse/CASSANDRA-8463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14249047#comment-14249047 ] Rick Branson commented on CASSANDRA-8463: - It did take some time to rebalance

[jira] [Updated] (CASSANDRA-8463) Constant compaction under LCS

[ https://issues.apache.org/jira/browse/CASSANDRA-8463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick Branson updated CASSANDRA-8463: Summary: Constant compaction under LCS (was: Upgrading 2.0 to 2.1 causes LCS to

[jira] [Commented] (CASSANDRA-8463) Constant compaction under LCS

[ https://issues.apache.org/jira/browse/CASSANDRA-8463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14246905#comment-14246905 ] Rick Branson commented on CASSANDRA-8463: - It looks like this is just a

[jira] [Commented] (CASSANDRA-8463) Constant compaction under LCS

[ https://issues.apache.org/jira/browse/CASSANDRA-8463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14247061#comment-14247061 ] Rick Branson commented on CASSANDRA-8463: - Writes had to be turned off to this

[jira] [Commented] (CASSANDRA-8463) Constant compaction under LCS

[ https://issues.apache.org/jira/browse/CASSANDRA-8463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14247293#comment-14247293 ] Rick Branson commented on CASSANDRA-8463: - I applied the logging patch on one

[jira] [Commented] (CASSANDRA-8463) Constant compaction under LCS

[ https://issues.apache.org/jira/browse/CASSANDRA-8463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14247337#comment-14247337 ] Rick Branson commented on CASSANDRA-8463: - This also seems suspect for

[jira] [Commented] (CASSANDRA-8462) Upgrading a 2.0 to 2.1 breaks CFMetaData on 2.0 nodes

[ https://issues.apache.org/jira/browse/CASSANDRA-8462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14247499#comment-14247499 ] Rick Branson commented on CASSANDRA-8462: - [~iamaleksey] this happened first

[jira] [Updated] (CASSANDRA-8463) Upgrading 2.0 to 2.1 causes LCS to recompact all files

[ https://issues.apache.org/jira/browse/CASSANDRA-8463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick Branson updated CASSANDRA-8463: Attachment: log-for-8463.txt Upgrading 2.0 to 2.1 causes LCS to recompact all files

[jira] [Created] (CASSANDRA-8475) Altering Table's tombstone_threshold stalls compaction until restart

Rick Branson created CASSANDRA-8475: --- Summary: Altering Table's tombstone_threshold stalls compaction until restart Key: CASSANDRA-8475 URL: https://issues.apache.org/jira/browse/CASSANDRA-8475

[jira] [Commented] (CASSANDRA-8475) Altering Table's tombstone_threshold stalls compaction until restart

[ https://issues.apache.org/jira/browse/CASSANDRA-8475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14244887#comment-14244887 ] Rick Branson commented on CASSANDRA-8475: - Workaround for this is to disable

[jira] [Created] (CASSANDRA-8462) Upgrading a 2.0 to 2.1 breaks CFMetaData on 2.0 nodes

Rick Branson created CASSANDRA-8462: --- Summary: Upgrading a 2.0 to 2.1 breaks CFMetaData on 2.0 nodes Key: CASSANDRA-8462 URL: https://issues.apache.org/jira/browse/CASSANDRA-8462 Project: Cassandra

[jira] [Created] (CASSANDRA-8463) Upgrading 2.0 to 2.1 causes LCS to recompact all files

Rick Branson created CASSANDRA-8463: --- Summary: Upgrading 2.0 to 2.1 causes LCS to recompact all files Key: CASSANDRA-8463 URL: https://issues.apache.org/jira/browse/CASSANDRA-8463 Project: Cassandra

[jira] [Created] (CASSANDRA-7764) RFC: Range movements will wake up previously invisible data

Rick Branson created CASSANDRA-7764: --- Summary: RFC: Range movements will wake up previously invisible data Key: CASSANDRA-7764 URL: https://issues.apache.org/jira/browse/CASSANDRA-7764 Project:

[jira] [Commented] (CASSANDRA-7246) Gossip Null Pointer Exception when a cassandra instance in ring is restarted

[ https://issues.apache.org/jira/browse/CASSANDRA-7246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14095965#comment-14095965 ] Rick Branson commented on CASSANDRA-7246: - Got some similar NPEs on restart on

[jira] [Created] (CASSANDRA-7758) Some gossip messages are very slow to process on vnode clusters

Rick Branson created CASSANDRA-7758: --- Summary: Some gossip messages are very slow to process on vnode clusters Key: CASSANDRA-7758 URL: https://issues.apache.org/jira/browse/CASSANDRA-7758 Project:

[jira] [Updated] (CASSANDRA-7758) Some gossip messages are very slow to process on vnode clusters

[ https://issues.apache.org/jira/browse/CASSANDRA-7758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick Branson updated CASSANDRA-7758: Attachment: 7758-1-v1.2.txt Some gossip messages are very slow to process on vnode

[jira] [Updated] (CASSANDRA-7758) Some gossip messages are very slow to process on vnode clusters

[ https://issues.apache.org/jira/browse/CASSANDRA-7758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick Branson updated CASSANDRA-7758: Attachment: 7758-1-v2.0.txt Some gossip messages are very slow to process on vnode

[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 ] Rick Branson updated CASSANDRA-7704: Attachment: other-errors.txt There wasn't anything in the logs that indicated *why*

[jira] [Updated] (CASSANDRA-7664) IndexOutOfBoundsException thrown during repair

[ https://issues.apache.org/jira/browse/CASSANDRA-7664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick Branson updated CASSANDRA-7664: Attachment: other-errors.txt Got this on a bootstrapping node shortly after a stream

[jira] [Commented] (CASSANDRA-6335) Hints broken for nodes that change broadcast address

[ https://issues.apache.org/jira/browse/CASSANDRA-6335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14091142#comment-14091142 ] Rick Branson commented on CASSANDRA-6335: - Easiest way to repro might be to

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

Rick Branson created CASSANDRA-7704: --- Summary: FileNotFoundException during STREAM-OUT triggers 100% CPU usage Key: CASSANDRA-7704 URL: https://issues.apache.org/jira/browse/CASSANDRA-7704 Project:

[jira] [Commented] (CASSANDRA-7432) Add new CMS GC flags to cassandra_env.sh for JVM later than 1.7.0_60

[ https://issues.apache.org/jira/browse/CASSANDRA-7432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14084927#comment-14084927 ] Rick Branson commented on CASSANDRA-7432: - Very happy with this in production.

[jira] [Created] (CASSANDRA-7594) Disruptor Thrift server worker thread pool not adjustable

Rick Branson created CASSANDRA-7594: --- Summary: Disruptor Thrift server worker thread pool not adjustable Key: CASSANDRA-7594 URL: https://issues.apache.org/jira/browse/CASSANDRA-7594 Project:

[jira] [Commented] (CASSANDRA-7594) Disruptor Thrift server worker thread pool not adjustable

[ https://issues.apache.org/jira/browse/CASSANDRA-7594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14071975#comment-14071975 ] Rick Branson commented on CASSANDRA-7594: - The ideal situation would be if

[jira] [Commented] (CASSANDRA-5239) Asynchronous (non-blocking) StorageProxy

[ https://issues.apache.org/jira/browse/CASSANDRA-5239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14072002#comment-14072002 ] Rick Branson commented on CASSANDRA-5239: - That is an epic patch [~slebresne].

[jira] [Commented] (CASSANDRA-5239) Asynchronous (non-blocking) StorageProxy

[ https://issues.apache.org/jira/browse/CASSANDRA-5239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14072265#comment-14072265 ] Rick Branson commented on CASSANDRA-5239: - [~benedict]: Not sure I follow how

[jira] [Commented] (CASSANDRA-7402) limit the on heap memory available to requests

[ https://issues.apache.org/jira/browse/CASSANDRA-7402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14055168#comment-14055168 ] Rick Branson commented on CASSANDRA-7402: - The more practical thing here is to

[jira] [Commented] (CASSANDRA-7486) Compare CMS and G1 pause times

[ https://issues.apache.org/jira/browse/CASSANDRA-7486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14050677#comment-14050677 ] Rick Branson commented on CASSANDRA-7486: - Mad anecdotes: We ran with G1

[jira] [Commented] (CASSANDRA-6621) STCS fallback is not optimal when bootstrapping

[ https://issues.apache.org/jira/browse/CASSANDRA-6621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14043921#comment-14043921 ] Rick Branson commented on CASSANDRA-6621: - How about we add a switch to

[jira] [Commented] (CASSANDRA-6621) STCS fallback is not optimal when bootstrapping

[ https://issues.apache.org/jira/browse/CASSANDRA-6621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14043976#comment-14043976 ] Rick Branson commented on CASSANDRA-6621: - As I said above, it causes

[jira] [Commented] (CASSANDRA-6621) STCS fallback is not optimal when bootstrapping

[ https://issues.apache.org/jira/browse/CASSANDRA-6621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14026916#comment-14026916 ] Rick Branson commented on CASSANDRA-6621: - This is definitely sub-optimal for

[jira] [Commented] (CASSANDRA-7262) During streaming: java.lang.AssertionError: Reference counter -1

[ https://issues.apache.org/jira/browse/CASSANDRA-7262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14012902#comment-14012902 ] Rick Branson commented on CASSANDRA-7262: - Also seeing this NPE: at

[jira] [Commented] (CASSANDRA-7262) During streaming: java.lang.AssertionError: Reference counter -1

[ https://issues.apache.org/jira/browse/CASSANDRA-7262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14012015#comment-14012015 ] Rick Branson commented on CASSANDRA-7262: - Would this cause all of the

[jira] [Comment Edited] (CASSANDRA-7262) During streaming: java.lang.AssertionError: Reference counter -1

[ https://issues.apache.org/jira/browse/CASSANDRA-7262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14012015#comment-14012015 ] Rick Branson edited comment on CASSANDRA-7262 at 5/29/14 3:28 AM:

[jira] [Created] (CASSANDRA-7309) Explicit limit for maximum number of Thrift connections

Rick Branson created CASSANDRA-7309: --- Summary: Explicit limit for maximum number of Thrift connections Key: CASSANDRA-7309 URL: https://issues.apache.org/jira/browse/CASSANDRA-7309 Project:

[jira] [Commented] (CASSANDRA-6285) 2.0 HSHA server introduces corrupt data

[ https://issues.apache.org/jira/browse/CASSANDRA-6285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14002142#comment-14002142 ] Rick Branson commented on CASSANDRA-6285: - Haven't been able to repro in over

[jira] [Reopened] (CASSANDRA-6285) 2.0 HSHA server introduces corrupt data

[ https://issues.apache.org/jira/browse/CASSANDRA-6285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick Branson reopened CASSANDRA-6285: - Reproduced In: 2.0.6 (was: 2.0.2) This is not fixed. Still seeing the same

[jira] [Commented] (CASSANDRA-6285) 2.0 HSHA server introduces corrupt data

[ https://issues.apache.org/jira/browse/CASSANDRA-6285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13996712#comment-13996712 ] Rick Branson commented on CASSANDRA-6285: - I think what might help this

[jira] [Commented] (CASSANDRA-6285) 2.0 HSHA server introduces corrupt data

[ https://issues.apache.org/jira/browse/CASSANDRA-6285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13996899#comment-13996899 ] Rick Branson commented on CASSANDRA-6285: - I did some more digging around on

[jira] [Commented] (CASSANDRA-6815) Decided if we want to bring back thrift HSHA in 2.0.7

[ https://issues.apache.org/jira/browse/CASSANDRA-6815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13993814#comment-13993814 ] Rick Branson commented on CASSANDRA-6815: - FYI I reopened CASSANDRA-6285

[jira] [Commented] (CASSANDRA-6996) Setting severity via JMX broken

[ https://issues.apache.org/jira/browse/CASSANDRA-6996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13977068#comment-13977068 ] Rick Branson commented on CASSANDRA-6996: - LGTM, works on a test box.

[jira] [Commented] (CASSANDRA-6961) nodes should go into hibernate when join_ring is false

[ https://issues.apache.org/jira/browse/CASSANDRA-6961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13964626#comment-13964626 ] Rick Branson commented on CASSANDRA-6961: - Very happy about this. It will make

[jira] [Commented] (CASSANDRA-6757) SliceQueryFilter can accept multiple ColumnSlice but not exposed to thrift

[ https://issues.apache.org/jira/browse/CASSANDRA-6757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13964961#comment-13964961 ] Rick Branson commented on CASSANDRA-6757: - *begs for 2.1 version of this*

[jira] [Created] (CASSANDRA-6992) Bootstrap on vnodes clusters can cause stampeding/storm behavior

Rick Branson created CASSANDRA-6992: --- Summary: Bootstrap on vnodes clusters can cause stampeding/storm behavior Key: CASSANDRA-6992 URL: https://issues.apache.org/jira/browse/CASSANDRA-6992

[jira] [Created] (CASSANDRA-6996) Setting severity via JMX broken

Rick Branson created CASSANDRA-6996: --- Summary: Setting severity via JMX broken Key: CASSANDRA-6996 URL: https://issues.apache.org/jira/browse/CASSANDRA-6996 Project: Cassandra Issue Type:

[jira] [Commented] (CASSANDRA-6685) Nodes never bootstrap if schema is empty

[ https://issues.apache.org/jira/browse/CASSANDRA-6685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13944211#comment-13944211 ] Rick Branson commented on CASSANDRA-6685: - Ran into this today trying to test

[jira] [Commented] (CASSANDRA-6285) 2.0 HSHA server introduces corrupt data

[ https://issues.apache.org/jira/browse/CASSANDRA-6285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13923245#comment-13923245 ] Rick Branson commented on CASSANDRA-6285: - Unfortunately this hit us during

[jira] [Commented] (CASSANDRA-6285) 2.0 HSHA server introduces corrupt data

[ https://issues.apache.org/jira/browse/CASSANDRA-6285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13923441#comment-13923441 ] Rick Branson commented on CASSANDRA-6285: - We put in the

[jira] [Commented] (CASSANDRA-6285) 2.0 HSHA server introduces corrupt data

[ https://issues.apache.org/jira/browse/CASSANDRA-6285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13923466#comment-13923466 ] Rick Branson commented on CASSANDRA-6285: - [~xedin]: We had perf issues with

[jira] [Commented] (CASSANDRA-6285) 2.0 HSHA server introduces corrupt data

[ https://issues.apache.org/jira/browse/CASSANDRA-6285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13923514#comment-13923514 ] Rick Branson commented on CASSANDRA-6285: - [~xedin]: off-heap for disruptor.

[jira] [Updated] (CASSANDRA-6592) IllegalArgumentException when Preparing Statements

[ https://issues.apache.org/jira/browse/CASSANDRA-6592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick Branson updated CASSANDRA-6592: Priority: Critical (was: Minor) IllegalArgumentException when Preparing Statements

[jira] [Commented] (CASSANDRA-6569) Batchlog replays copy the entire batchlog table into the heap

[ https://issues.apache.org/jira/browse/CASSANDRA-6569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13869618#comment-13869618 ] Rick Branson commented on CASSANDRA-6569: - Looks like deleteBatch got switched

[jira] [Commented] (CASSANDRA-6569) Batchlog replays copy the entire batchlog table into the heap

[ https://issues.apache.org/jira/browse/CASSANDRA-6569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13869620#comment-13869620 ] Rick Branson commented on CASSANDRA-6569: - Also, would it be possible to get

[jira] [Created] (CASSANDRA-6569) Batchlog replays copy the entire batchlog table into the heap

Rick Branson created CASSANDRA-6569: --- Summary: Batchlog replays copy the entire batchlog table into the heap Key: CASSANDRA-6569 URL: https://issues.apache.org/jira/browse/CASSANDRA-6569 Project:

[jira] [Created] (CASSANDRA-6551) Rack-aware batchlog replication

Rick Branson created CASSANDRA-6551: --- Summary: Rack-aware batchlog replication Key: CASSANDRA-6551 URL: https://issues.apache.org/jira/browse/CASSANDRA-6551 Project: Cassandra Issue Type:

[jira] [Updated] (CASSANDRA-6551) Rack-aware batchlog replication

[ https://issues.apache.org/jira/browse/CASSANDRA-6551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick Branson updated CASSANDRA-6551: Component/s: Core Reproduced In: 2.0.4, 1.2.13 Fix Version/s: 2.0.5

[jira] [Updated] (CASSANDRA-6488) Batchlog writes consume unnecessarily large amounts of CPU on vnodes clusters

[ https://issues.apache.org/jira/browse/CASSANDRA-6488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick Branson updated CASSANDRA-6488: Attachment: graph (21).png CPU usage dropping on a production cluster after the

[jira] [Created] (CASSANDRA-6488) Batchlog writes consume unnecessarily large amounts of CPU on vnodes clusters

Rick Branson created CASSANDRA-6488: --- Summary: Batchlog writes consume unnecessarily large amounts of CPU on vnodes clusters Key: CASSANDRA-6488 URL: https://issues.apache.org/jira/browse/CASSANDRA-6488

[jira] [Updated] (CASSANDRA-6488) Batchlog writes consume unnecessarily large amounts of CPU on vnodes clusters

[ https://issues.apache.org/jira/browse/CASSANDRA-6488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick Branson updated CASSANDRA-6488: Attachment: 6488-rbranson-patch.txt Batchlog writes consume unnecessarily large

[jira] [Commented] (CASSANDRA-6485) NPE in calculateNaturalEndpoints

[ https://issues.apache.org/jira/browse/CASSANDRA-6485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13848118#comment-13848118 ] Rick Branson commented on CASSANDRA-6485: - LGTM. NPE in

[jira] [Commented] (CASSANDRA-6345) Endpoint cache invalidation causes CPU spike (on vnode rings?)

[ https://issues.apache.org/jira/browse/CASSANDRA-6345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13832783#comment-13832783 ] Rick Branson commented on CASSANDRA-6345: - Thanks for taking the time to

[jira] [Comment Edited] (CASSANDRA-6345) Endpoint cache invalidation causes CPU spike (on vnode rings?)

[ https://issues.apache.org/jira/browse/CASSANDRA-6345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13832783#comment-13832783 ] Rick Branson edited comment on CASSANDRA-6345 at 11/26/13 5:34 PM:

[jira] [Commented] (CASSANDRA-5357) Query cache

[ https://issues.apache.org/jira/browse/CASSANDRA-5357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13832901#comment-13832901 ] Rick Branson commented on CASSANDRA-5357: - Perhaps an anecdote from a

[jira] [Commented] (CASSANDRA-6345) Endpoint cache invalidation causes CPU spike (on vnode rings?)

[ https://issues.apache.org/jira/browse/CASSANDRA-6345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13833150#comment-13833150 ] Rick Branson commented on CASSANDRA-6345: - LGTM! Endpoint cache invalidation

[jira] [Created] (CASSANDRA-6408) Efficient multi-partition mutations

Rick Branson created CASSANDRA-6408: --- Summary: Efficient multi-partition mutations Key: CASSANDRA-6408 URL: https://issues.apache.org/jira/browse/CASSANDRA-6408 Project: Cassandra Issue

[jira] [Commented] (CASSANDRA-6345) Endpoint cache invalidation causes CPU spike (on vnode rings?)

[ https://issues.apache.org/jira/browse/CASSANDRA-6345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13828097#comment-13828097 ] Rick Branson commented on CASSANDRA-6345: - +100 at removing those pub/sub

[jira] [Commented] (CASSANDRA-6345) Endpoint cache invalidation causes CPU spike (on vnode rings?)

[ https://issues.apache.org/jira/browse/CASSANDRA-6345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13825614#comment-13825614 ] Rick Branson commented on CASSANDRA-6345: - I like the simpler approach. I

[jira] [Created] (CASSANDRA-6354) No cleanup of excess gossip connections

Rick Branson created CASSANDRA-6354: --- Summary: No cleanup of excess gossip connections Key: CASSANDRA-6354 URL: https://issues.apache.org/jira/browse/CASSANDRA-6354 Project: Cassandra

[jira] [Commented] (CASSANDRA-6345) Endpoint cache invalidation causes CPU spike (on vnode rings?)

[ https://issues.apache.org/jira/browse/CASSANDRA-6345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13823274#comment-13823274 ] Rick Branson commented on CASSANDRA-6345: - Unfortunately both of the patches

[jira] [Updated] (CASSANDRA-6345) Endpoint cache invalidation causes CPU spike (on vnode rings?)

[ https://issues.apache.org/jira/browse/CASSANDRA-6345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick Branson updated CASSANDRA-6345: Attachment: 6345-rbranson-v2.txt Attached a new patch with the deadlock fixed. We're

[jira] [Created] (CASSANDRA-6345) Endpoint cache invalidation causes CPU spike (on vnode rings?)

Rick Branson created CASSANDRA-6345: --- Summary: Endpoint cache invalidation causes CPU spike (on vnode rings?) Key: CASSANDRA-6345 URL: https://issues.apache.org/jira/browse/CASSANDRA-6345 Project:

[jira] [Updated] (CASSANDRA-6345) Endpoint cache invalidation causes CPU spike (on vnode rings?)

[ https://issues.apache.org/jira/browse/CASSANDRA-6345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick Branson updated CASSANDRA-6345: Reproduced In: 1.2.11 Endpoint cache invalidation causes CPU spike (on vnode rings?)

[jira] [Updated] (CASSANDRA-6345) Endpoint cache invalidation causes CPU spike (on vnode rings?)

[ https://issues.apache.org/jira/browse/CASSANDRA-6345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick Branson updated CASSANDRA-6345: Attachment: 6345.txt Attached a patch we deployed to production that fixed the issue.

[jira] [Updated] (CASSANDRA-6345) Endpoint cache invalidation causes CPU spike (on vnode rings?)

[ https://issues.apache.org/jira/browse/CASSANDRA-6345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick Branson updated CASSANDRA-6345: Attachment: (was: 6345.txt) Endpoint cache invalidation causes CPU spike (on

[jira] [Updated] (CASSANDRA-6345) Endpoint cache invalidation causes CPU spike (on vnode rings?)

[ https://issues.apache.org/jira/browse/CASSANDRA-6345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick Branson updated CASSANDRA-6345: Attachment: 6345-rbranson.txt Endpoint cache invalidation causes CPU spike (on vnode

[jira] [Updated] (CASSANDRA-6345) Endpoint cache invalidation causes CPU spike (on vnode rings?)

[ https://issues.apache.org/jira/browse/CASSANDRA-6345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick Branson updated CASSANDRA-6345: Attachment: half-way-thru-6345-rbranson-patch-applied.png CPU user% graph during the

[jira] [Commented] (CASSANDRA-6345) Endpoint cache invalidation causes CPU spike (on vnode rings?)

[ https://issues.apache.org/jira/browse/CASSANDRA-6345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13822027#comment-13822027 ] Rick Branson commented on CASSANDRA-6345: - Well, I started writing the patch

[jira] [Created] (CASSANDRA-6334) Option to not listen on Thrift/CQL if cluster is N nodes

Rick Branson created CASSANDRA-6334: --- Summary: Option to not listen on Thrift/CQL if cluster is N nodes Key: CASSANDRA-6334 URL: https://issues.apache.org/jira/browse/CASSANDRA-6334 Project:

[jira] [Created] (CASSANDRA-6335) Hints broken for nodes that change broadcast address

Rick Branson created CASSANDRA-6335: --- Summary: Hints broken for nodes that change broadcast address Key: CASSANDRA-6335 URL: https://issues.apache.org/jira/browse/CASSANDRA-6335 Project: Cassandra

[jira] [Commented] (CASSANDRA-6335) Hints broken for nodes that change broadcast address

[ https://issues.apache.org/jira/browse/CASSANDRA-6335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13820415#comment-13820415 ] Rick Branson commented on CASSANDRA-6335: - It looks like it stalls the hint

[jira] [Comment Edited] (CASSANDRA-6335) Hints broken for nodes that change broadcast address

[ https://issues.apache.org/jira/browse/CASSANDRA-6335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13820415#comment-13820415 ] Rick Branson edited comment on CASSANDRA-6335 at 11/12/13 8:41 PM:

[jira] [Commented] (CASSANDRA-6106) QueryState.getTimestamp() FBUtilities.timestampMicros() reads current timestamp with System.currentTimeMillis() * 1000 instead of System.nanoTime() / 1000

[ https://issues.apache.org/jira/browse/CASSANDRA-6106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13779564#comment-13779564 ] Rick Branson commented on CASSANDRA-6106: - Could this re-sample the base

[jira] [Commented] (CASSANDRA-6106) QueryState.getTimestamp() FBUtilities.timestampMicros() reads current timestamp with System.currentTimeMillis() * 1000 instead of System.nanoTime() / 1000

[ https://issues.apache.org/jira/browse/CASSANDRA-6106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13779573#comment-13779573 ] Rick Branson commented on CASSANDRA-6106: - I think you'd actually have to use

[jira] [Commented] (CASSANDRA-6106) QueryState.getTimestamp() FBUtilities.timestampMicros() reads current timestamp with System.currentTimeMillis() * 1000 instead of System.nanoTime() / 1000

[ https://issues.apache.org/jira/browse/CASSANDRA-6106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13779586#comment-13779586 ] Rick Branson commented on CASSANDRA-6106: - Yeah you're right. The thread will

[jira] [Commented] (CASSANDRA-5948) StreamOut doesn't correctly handle wrapped ranges

[ https://issues.apache.org/jira/browse/CASSANDRA-5948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13758245#comment-13758245 ] Rick Branson commented on CASSANDRA-5948: - Curious what the impact of this

[jira] [Created] (CASSANDRA-5966) Average name query performance much worse for wide rows

Rick Branson created CASSANDRA-5966: --- Summary: Average name query performance much worse for wide rows Key: CASSANDRA-5966 URL: https://issues.apache.org/jira/browse/CASSANDRA-5966 Project:

[jira] [Updated] (CASSANDRA-5966) Average name query performance much worse for wide rows

[ https://issues.apache.org/jira/browse/CASSANDRA-5966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick Branson updated CASSANDRA-5966: Attachment: 5966.txt Attached patch modifies SSTableNamesIterator to stop

[jira] [Updated] (CASSANDRA-5966) Average name query performance much worse for wide rows

[ https://issues.apache.org/jira/browse/CASSANDRA-5966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick Branson updated CASSANDRA-5966: Attachment: 5966-v2.txt Average name query performance much worse for wide rows

  1   2   >