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 91187185D9 for ; Wed, 29 Jul 2015 01:29:42 +0000 (UTC) Received: (qmail 49830 invoked by uid 500); 29 Jul 2015 01:29:38 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 49791 invoked by uid 500); 29 Jul 2015 01:29:38 -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 49781 invoked by uid 99); 29 Jul 2015 01:29:38 -0000 Received: from Unknown (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 29 Jul 2015 01:29:38 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 15B21192C06 for ; Wed, 29 Jul 2015 01:29:38 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 5.001 X-Spam-Level: ***** X-Spam-Status: No, score=5.001 tagged_above=-999 required=6.31 tests=[HTML_MESSAGE=3, KAM_BADIPHTTP=2, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, WEIRD_PORT=0.001] autolearn=disabled Received: from mx1-us-west.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id mvyNkbVoBuht for ; Wed, 29 Jul 2015 01:29:29 +0000 (UTC) Received: from mail-io0-f182.google.com (mail-io0-f182.google.com [209.85.223.182]) by mx1-us-west.apache.org (ASF Mail Server at mx1-us-west.apache.org) with ESMTPS id 4F0D92156D for ; Wed, 29 Jul 2015 01:29:29 +0000 (UTC) Received: by ioii16 with SMTP id i16so6182338ioi.0 for ; Tue, 28 Jul 2015 18:28:43 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=YOj5u3GFVlbFltkmBW5NclE9y6brhyOI015wEGisAiA=; b=BI9nuVXW9IS255W2c8lAWWcv3Xl/wCZ7CwI+6gsoAZdl/2zNZ7hZR8rzyxlndWB+l6 438aM/1CzbEY8ADiLfTvZzAtMWXgUYSi033LM7a8C08nmzeJIuuPGzbKQd5XD7nf+LqU LPSLtAIIdD4pacsoTtlrUWyKE08AdhRy9AvcsghUol8usEE2DCIu4hawF69tzyw2hlfj b6g86+THYJHteqWgMrEts62wQ3dVFubSTPpZrriUqGqSMCoY8w4FVTDlevdKfZn/8uYm 1fuL2sZoWiYsFHB70MxxFPVkLoDQBW+aZKZSVUunh0baFgZSzWqPGez3TjGEA3XTQcjY lcBg== X-Gm-Message-State: ALoCoQnNNZo1f+QXe63q4lrq4ZO7NoqfUNlJYzBzB+/guufp4KY571jEIembYOFDxwNRExbrgVeu MIME-Version: 1.0 X-Received: by 10.107.18.224 with SMTP id 93mr60189542ios.51.1438133323520; Tue, 28 Jul 2015 18:28:43 -0700 (PDT) Received: by 10.36.98.72 with HTTP; Tue, 28 Jul 2015 18:28:43 -0700 (PDT) In-Reply-To: <1436482349590.7c3c18a7@Nodemailer> References: <6B8C8247-ED96-464B-AF45-726547B2E992@zen-innovations.com> <1436482349590.7c3c18a7@Nodemailer> Date: Tue, 28 Jul 2015 18:28:43 -0700 Message-ID: Subject: Re: Is there a way to remove a node with Opscenter? From: Sid Tantia To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=001a113ecc56e374ea051bf981f0 --001a113ecc56e374ea051bf981f0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I know this is an old thread but just FYI for others having the same problem (OpsCenter trying to connect to node that is already removed)...the solution is to ssh into the OpsCenter node and run `sudo service opscenterd restart` On Thu, Jul 9, 2015 at 3:52 PM, Sid Tantia wrote: > Found my mistake: I was typing the command on the node I was trying to > remove from the cluster. After trying the command on another node in the > cluster, it worked (`nodetool status` shows the node as removed), however > OpsCenter still does not recognize the node as removed. > > Any ways to fix OpsCenter so that it stops trying to connect to the node > that is already removed? > > > > On Tue, Jul 7, 2015 at 11:38 PM, Jean Tremblay < > jean.tremblay@zen-innovations.com> wrote: > >> When you do a nodetool command and you don=E2=80=99t specify a hostname,= it sends >> the requests via JMX to the localhost node. If that node is down then th= e >> command will not succeed. >> In your case you are probably doing the command from a machine which has >> not cassandra running, in that case you need to specify a node with the >> switch -h. >> >> So for your that would be: >> >> nodetool -h removenode >> >> where is the address of a server which has cassandra >> daemon running. >> >> Cheers >> >> Jean >> >> On 08 Jul 2015, at 01:39 , Sid Tantia >> wrote: >> >> I tried both `nodetool remove node ` and `nodetool decommission= ` >> and they both give the error: >> >> nodetool: Failed to connect to '127.0.0.1:7199' - ConnectException: >> 'Connection refused=E2=80=99. >> >> Here is what I have tried to fix this: >> >> 1) Uncommented JVM_OPTS=3D=E2=80=9D$JVM_OPTS -Djava.rmi.server.hostname= =3D> name>=E2=80=9D >> 2) Changed rpc_address to 0.0.0.0 >> 3) Restarted cassandra >> 4) Restarted datastax-agent >> >> (Note that I installed my cluster using opscenter so that may have >> something to do with it? ) >> >> >> >> On Tue, Jul 7, 2015 at 2:08 PM, Surbhi Gupta >> wrote: >> >>> If node is down use : >>> >>> nodetool removenode >>> >>> We have to run the below command when the node is down & if the cluster >>> does not use vnodes, before running the nodetool removenode command, ad= just >>> the tokens. >>> >>> If the node is up, then the command would be =E2=80=9Cnodetool decommis= sion=E2=80=9D to >>> remove the node. >>> >>> Remove the node from the =E2=80=9Cseed list=E2=80=9D within the configu= ration >>> cassandra.yaml. >>> >>> On 7 July 2015 at 12:56, Sid Tantia >>> wrote: >>> >>>> Thanks for the response. I=E2=80=99m trying to remove a node that=E2= =80=99s already >>>> down for some reason so its not allowing me to decommission it, is the= re >>>> some other way to do this? >>>> >>>> >>>> >>>> On Tue, Jul 7, 2015 at 12:45 PM, Kiran mk >>>> wrote: >>>> >>>>> Yes, if your intension is to decommission a node. You can do that >>>>> by clicking on the node and decommission. >>>>> >>>>> Best Regards, >>>>> Kiran.M.K. >>>>> On Jul 8, 2015 1:00 AM, "Sid Tantia" >>>>> wrote: >>>>> >>>>>> I know you can use `nodetool removenode` from the command line but >>>>>> is there a way to remove a node from a cluster using OpsCenter? >>>>>> >>>>>> >>>> >>> >> >> > --001a113ecc56e374ea051bf981f0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I know this is an old thread but just FYI for others havin= g the same problem (OpsCenter trying to connect to node that is already rem= oved)...the solution is to ssh into the OpsCenter node and run `sudo servic= e opscenterd restart`

On Thu, Jul 9, 2015 at 3:52 PM, Sid Tantia <= sid.tan= tia@baseboxsoftware.com> wrote:
Found my mistake: I was typing the command on the node I was trying t= o remove from the cluster. After trying the command on another node in the = cluster, it worked (`nodetool status` shows the node as removed), however O= psCenter still does not recognize the node as removed.

Any ways to fix OpsCenter so that it stops trying to connect to the no= de that is already removed?=C2=A0



On Tue, Jul 7, 2015 at 11:38 PM, Jean= Tremblay <jean.tremblay@zen-innovations.com> wrote:

When you do a nodetool command and you don=E2=80=99t specify a hostname, it= sends the requests via JMX to the localhost node. If that node is down the= n the command will not succeed.
In your case you are probably doing the command from a machine which h= as not cassandra running, in that case you need to specify a node with the = switch -h.

So for your that would be:

nodetool -h <a-node-ip-address> removenode <Host ID>

where <a-node-ip-address> is the address of a server which has c= assandra daemon running.

Cheers

Jean

On 08 Jul 2015, at 01:39 , Sid Tantia <sid.tantia@baseboxsoftware.com&= gt; wrote:

I tried both `nodetool remove node <Host ID>` and `nodetool dec= ommission` and they both give the error:

nodetool: Failed to connect to '127.0.0.1:7199' - ConnectException: 'Connecti= on refused=E2=80=99.

Here is what I have tried to fix this:

1) Uncommented JVM_OPTS=3D=E2=80=9D$JVM_OPTS -Djava.rmi.server.hostnam= e=3D<public name>=E2=80=9D
2) Changed rpc_address to 0.0.0.0
3) Restarted cassandra
4) Restarted datastax-agent

(Note that I installed my cluster using opscenter so that may have som= ething to do with it? )



On Tue, Jul 7, 2015 at 2:08 PM, Surbhi Gupta <surbhi.gu= pta01@gmail.com> wrote:

If node is down use :

nodetool removenode <Host ID>

We have to run the below command when the node is down & if th= e cluster does not use vnodes, before running the nodetool removenode comma= nd, adjust the tokens.

If the node is up, then the command would be =E2=80=9Cnodetool dec= ommission=E2=80=9D to remove the node.


Remove the node from the =E2=80=9Cseed list=E2=80=9D within the co= nfiguration cassandra.yaml.


On 7 July 2015 at 12:56, Sid Tantia <sid= .tantia@baseboxsoftware.com> wrote:
Thanks for the response. I=E2=80=99m trying to remove a node that=E2= =80=99s already down for some reason so its not allowing me to decommission= it, is there some other way to do this?



On Tue, Jul 7, 2015 at 12:45 PM, Kiran mk <coolkiran2006@gmail.c= om> wrote:

Yes, if your intension is to decommission a node.=C2=A0 You = can do that by clicking on the node and decommission.

Best Regards,
Kiran.M.K.

On Jul 8, 2015 1:00 AM, "Sid Tantia" &= lt;sid.= tantia@baseboxsoftware.com> wrote:
I know you can use `nodetool removenode` from the command line but is = there a way to remove a node from a cluster using OpsCenter?







--001a113ecc56e374ea051bf981f0--