From user-return-34640-apmail-cassandra-user-archive=cassandra.apache.org@cassandra.apache.org Mon Jun 17 18:03:50 2013 Return-Path: X-Original-To: apmail-cassandra-user-archive@www.apache.org Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id BFC3310469 for ; Mon, 17 Jun 2013 18:03:50 +0000 (UTC) Received: (qmail 54391 invoked by uid 500); 17 Jun 2013 18:03:48 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 54357 invoked by uid 500); 17 Jun 2013 18:03:47 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 54343 invoked by uid 99); 17 Jun 2013 18:03:47 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 17 Jun 2013 18:03:47 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,HTML_OBFUSCATE_05_10,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of andreas.josef.wagner@googlemail.com designates 74.125.83.54 as permitted sender) Received: from [74.125.83.54] (HELO mail-ee0-f54.google.com) (74.125.83.54) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 17 Jun 2013 18:03:42 +0000 Received: by mail-ee0-f54.google.com with SMTP id t10so2014716eei.41 for ; Mon, 17 Jun 2013 11:03:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type; bh=01nhuIWANfRsALZxvSuCzX9vB+02vq7Ty8GUWR869Z0=; b=Wf461je5FL6JZSIj7eGc8+jOR//XoGqu1RvxrVxo0/5rXpnN5wfCTN+/zgL51Xe9Zz VTeDNq//6rjbO1J7faQKXpuuINvEsCzMaidP1wE0tBJ8EidRxZ6cfGumbkmKwsE/ZBZ9 bXKB86+m4EYZVTdYB9C6c/W/Nt495n+j26x2lC15o752nI8Sftd9kvRKJ/VL0uSChYe1 5T3Syj25JINNsvucU9x498QLSrvHYjQQ23Wp+8eP4f+mZSIVi8dw9DgL9DMSxiZPdy69 5ifQWIeMfbojEAyCNJ6+L0CfaLKXHzkUlSJwYRzIxhgDWZICbJ3ldJro2ZVVgAUYETgA YKgQ== X-Received: by 10.14.6.198 with SMTP id 46mr18074857een.121.1371492201006; Mon, 17 Jun 2013 11:03:21 -0700 (PDT) Received: from [172.22.177.231] (nat.scc.kit.edu. [129.13.72.198]) by mx.google.com with ESMTPSA id bj46sm16408087eeb.13.2013.06.17.11.03.19 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 17 Jun 2013 11:03:20 -0700 (PDT) Message-ID: <51BF4F66.2030707@googlemail.com> Date: Mon, 17 Jun 2013 20:03:18 +0200 From: Andreas Wagner User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6 MIME-Version: 1.0 To: user@cassandra.apache.org Subject: Re: Uneven CPU load on a 4 node cluster References: In-Reply-To: Content-Type: multipart/alternative; boundary="------------000106070009000909050502" X-Virus-Checked: Checked by ClamAV on apache.org This is a multi-part message in MIME format. --------------000106070009000909050502 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi all, I'm experiencing very similar effects. Did you (or anyone for that matter) have/solvethis issue? I have a 3 node cluster with vnodes having the same #tokens (256). Infact, all nodes are configured identical and share similar/same hardware. Cassandra.yaml settings are fairly standard - nothing fancy. According to "nodetool status" command everything is perfectly balanced. Running "cassandra-stress -d node_ip1,node_ip2,node_ip3" causes a heavy load on node_ip1, while node_ip2/3 are almost idle. Data, however, seems to be distributed evenly. I even get "UnavailableException" for some keys to be inserted on node_ip1. I also tried a second run with the scheduling set to "roundrobin" and made use of the standard "throttlingoption". Unfortunately, nothing changed. Could someone please provide some pointersand/or insights what I'm doing wrong? Thanks so much! Andreas --------------000106070009000909050502 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hi all,

I'm experiencing very similar effects. Did you (or anyone for that matter) have/solve this issue?


I have a 3 node cluster with vnodes having the same #tokens (256). In fact, all nodes are configured identical and share similar/same hardware. Cassandra.yaml settings are fairly standard - nothing fancy.

According to "nodetool status" command everything is perfectly balanced. Running "cassandra-stress -d node_ip1,node_ip2,node_ip3" causes a heavy load on node_ip1, while
node_ip2/3 are almost idle. Data, however, seems to be distributed evenly. I even get "UnavailableException" for some keys to be inserted on node_ip1.

I also tried a second run with the scheduling set to "roundrobin" and made use of the standard "throttling option". Unfortunately, nothing changed.

Could someone please provide some pointers and/or insights what I'm doing wrong?

Thanks so much!
Andreas
--------------000106070009000909050502--