Return-Path: Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: (qmail 58946 invoked from network); 17 Apr 2011 19:24:01 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 17 Apr 2011 19:24:01 -0000 Received: (qmail 67871 invoked by uid 500); 17 Apr 2011 19:23:59 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 67847 invoked by uid 500); 17 Apr 2011 19:23:59 -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 67839 invoked by uid 99); 17 Apr 2011 19:23:59 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 17 Apr 2011 19:23:59 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FREEMAIL_FROM,HTML_FONT_SIZE_LARGE,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,RFC_ABUSE_POST,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of csharpplusproject@gmail.com designates 209.85.216.44 as permitted sender) Received: from [209.85.216.44] (HELO mail-qw0-f44.google.com) (209.85.216.44) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 17 Apr 2011 19:23:51 +0000 Received: by qwc23 with SMTP id 23so2863316qwc.31 for ; Sun, 17 Apr 2011 12:23:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:subject:from:to:in-reply-to:references :content-type:date:message-id:mime-version:x-mailer; bh=Y75XRiUiIXBz1dnOMXHqwz6WTCEH0RHE4sboUpYUZJY=; b=xYSHISIUUPuQVRcZvZwYhY4/BLe456npXs49goQHTG1N9PxzO4fRIb38ScrQHkO9Z5 j7VvcMPfZ0MkaekN4066dd5hDC0HRHxR7AT8gt3woJTocdehThfNLp9qNtXpNw1z0UD1 YenHYuvFYuGtU59IGvEuXeQuEC8rM9lpv2/6I= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:from:to:in-reply-to:references:content-type:date:message-id :mime-version:x-mailer; b=uuGderme6Jqw+h0aXz83I3v9ZnRn5y7JmRrupkhiwBDMM9e9Kp69UMBIKZbqmyBMTW QpRKJUcGD+5SItjXpiJjdFqbC72L+5VBCGxRtGUZWm+mvt8SoEJ4anFRvkYoQvan+sZp kKqh9nXYidKroMWL6Fm0aFT9z2hh6Ge8MHBVE= Received: by 10.224.9.77 with SMTP id k13mr2077746qak.1.1303068210559; Sun, 17 Apr 2011 12:23:30 -0700 (PDT) Received: from [192.168.2.101] (adsl-76-250-193-165.dsl.wlfrct.sbcglobal.net [76.250.193.165]) by mx.google.com with ESMTPS id t17sm3531529qcs.23.2011.04.17.12.23.29 (version=SSLv3 cipher=OTHER); Sun, 17 Apr 2011 12:23:29 -0700 (PDT) Subject: Re: Cassandra 0.7.4 Bug? From: csharpplusproject To: user@cassandra.apache.org In-Reply-To: References: <8747B84D-8AAB-4DDB-A4B5-215EC7962B03@cmu.edu> <64E44C90-0AAB-40E3-B972-FD94C3D6C02F@cmu.edu> <1303046246.6089.13194.camel@internet> Content-Type: multipart/alternative; boundary="=-DVzH6cUkL3pCXlXq43q3" Date: Sun, 17 Apr 2011 15:23:20 -0400 Message-ID: <1303068200.6089.13956.camel@internet> Mime-Version: 1.0 X-Mailer: Evolution 2.28.3 --=-DVzH6cUkL3pCXlXq43q3 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Shimi, Chag Sameach. Yes, I know that a restart solves this, yet, I think this is something that must be resolved as a result of 'nodetool move'. Shalom. -----Original Message----- From: shimi Reply-to: user@cassandra.apache.org To: user@cassandra.apache.org Subject: Re: Cassandra 0.7.4 Bug? Date: Sun, 17 Apr 2011 22:17:59 +0300 I had the same thing. Node restart should solve it. Shimi On Sun, Apr 17, 2011 at 4:25 PM, Dikang Gu wrote: +1. I also met this problem several days before, and I haven't got a solution yet... On Sun, Apr 17, 2011 at 9:17 PM, csharpplusproject wrote: Often, I see the following behavior: (1) Cassandra works, all nodes are up etc (2) a 'move' operation is being run on one of the nodes (3) following this 'move' operation, even after a couple of hours / days where it is obvious the operation has ended, the node which had 'moved' remains with a status of ? perhaps it's a bug? ___________________________________________________________________________________ shalom@host:/opt/cassandra/apache-cassandra-0.7.4$ bin/nodetool -host 192.168.0.5 ring Address Status State Load Owns Token 127605887595351923798765477786913079296 192.168.0.253 Up Normal 88.66 MB 25.00% 0 192.168.0.4 Up Normal 558.2 MB 50.00% 85070591730234615865843651857942052863 192.168.0.5 Up Normal 71.03 MB 16.67% 113427455640312821154458202477256070485 192.168.0.6 Up Normal 44.71 MB 8.33% 127605887595351923798765477786913079296 shalom@host:/opt/cassandra/apache-cassandra-0.7.4$ bin/nodetool -host 192.168.0.4 move 92535295865117307932921825928971026432 shalom@host:/opt/cassandra/apache-cassandra-0.7.4$ bin/nodetool -host 192.168.0.5 ring Address Status State Load Owns Token 127605887595351923798765477786913079296 192.168.0.253 Up Normal 171.17 MB 25.00% 0 192.168.0.4 ? Normal 212.11 MB 54.39% 92535295865117307932921825928971026432 192.168.0.5 Up Normal 263.91 MB 12.28% 113427455640312821154458202477256070485 192.168.0.6 Up Normal 26.21 MB 8.33% 127605887595351923798765477786913079296 -- Dikang Gu 0086 - 18611140205 --=-DVzH6cUkL3pCXlXq43q3 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: 7bit Shimi,

Chag Sameach. Yes, I know that a restart solves this, yet, I think this is something that must be resolved as a result of 'nodetool move'.

Shalom.

-----Original Message-----
From: shimi <shimi.k@gmail.com>
Reply-to: user@cassandra.apache.org
To: user@cassandra.apache.org
Subject: Re: Cassandra 0.7.4 Bug?
Date: Sun, 17 Apr 2011 22:17:59 +0300

I had the same thing.
Node restart should solve it.

Shimi


On Sun, Apr 17, 2011 at 4:25 PM, Dikang Gu <dikang85@gmail.com> wrote:
+1.


I also met this problem several days before, and I haven't got a solution yet...



On Sun, Apr 17, 2011 at 9:17 PM, csharpplusproject <csharpplusproject@gmail.com> wrote:
Often, I see the following behavior:

(1) Cassandra works, all nodes are up etc

(2) a 'move' operation is being run on one of the nodes

(3) following this 'move' operation, even after a couple of hours / days where it is obvious the operation has ended, the node which had 'moved' remains with a status of ?

perhaps it's a bug?

___________________________________________________________________________________

shalom@host:/opt/cassandra/apache-cassandra-0.7.4$ bin/nodetool -host 192.168.0.5 ring
Address         Status State   Load            Owns    Token                                      
                                                       127605887595351923798765477786913079296    
192.168.0.253   Up     Normal  88.66 MB        25.00%  0                                          
  192.168.0.4     Up     Normal  558.2 MB        50.00%  85070591730234615865843651857942052863     
  192.168.0.5     Up     Normal  71.03 MB        16.67%  113427455640312821154458202477256070485    
  192.168.0.6     Up     Normal  44.71 MB        8.33%   127605887595351923798765477786913079296    

shalom@host:/opt/cassandra/apache-cassandra-0.7.4$ bin/nodetool -host 192.168.0.4 move 92535295865117307932921825928971026432

shalom@host:/opt/cassandra/apache-cassandra-0.7.4$ bin/nodetool -host 192.168.0.5 ring
Address         Status State   Load            Owns    Token                                      
                                                       127605887595351923798765477786913079296    
192.168.0.253   Up     Normal  171.17 MB       25.00%  0                                          
192.168.0.4     ?      Normal  212.11 MB       54.39%  92535295865117307932921825928971026432     
192.168.0.5     Up     Normal  263.91 MB       12.28%  113427455640312821154458202477256070485    
192.168.0.6     Up     Normal  26.21 MB        8.33%   127605887595351923798765477786913079296    




--
Dikang Gu


0086 - 18611140205





--=-DVzH6cUkL3pCXlXq43q3--