[ https://issues.apache.org/jira/browse/CASSANDRA-6127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Quentin Conner updated CASSANDRA-6127: -------------------------------------- Attachment: 2013-11-05_18-09-38_compression_on_cpu_time.png Run against the following commit on cassandra-1.2 branch: 8e7d7285cdeac4f2527c933280d595bbddd26935 This profile measures CPU time, not elapsed time. Internode compression turned on. 256 nodes w/ num_tokens=256. GossipPeriod 1000 ms. ArrivalWindow.size() = 1000. > vnodes don't scale to hundreds of nodes > --------------------------------------- > > Key: CASSANDRA-6127 > URL: https://issues.apache.org/jira/browse/CASSANDRA-6127 > Project: Cassandra > Issue Type: Bug > Components: Core > Environment: Any cluster that has vnodes and consists of hundreds of > physical nodes. > Reporter: Tupshin Harper > Assignee: Jonathan Ellis > Attachments: 2013-11-05_18-09-38_compression_on_cpu_time.png, > 6000vnodes.patch, AdjustableGossipPeriod.patch, > delayEstimatorUntilStatisticallyValid.patch > > > There are a lot of gossip-related issues related to very wide clusters that > also have vnodes enabled. Let's use this ticket as a master in case there are > sub-tickets. > The most obvious symptom I've seen is with 1000 nodes in EC2 with m1.xlarge > instances. Each node configured with 32 vnodes. > Without vnodes, cluster spins up fine and is ready to handle requests within > 30 minutes or less. > With vnodes, nodes are reporting constant up/down flapping messages with no > external load on the cluster. After a couple of hours, they were still > flapping, had very high cpu load, and the cluster never looked like it was > going to stabilize or be useful for traffic. -- This message was sent by Atlassian JIRA (v6.1#6144)