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 <sid.tan...@baseboxsoftware.com> 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.tremb...@zen-innovations.com> wrote: > >> When you do a nodetool command and you don’t specify a hostname, it sends >> the requests via JMX to the localhost node. If that node is down then the >> 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 <a-node-ip-address> removenode <Host ID> >> >> where <a-node-ip-address> is the address of a server which has cassandra >> daemon running. >> >> Cheers >> >> Jean >> >> On 08 Jul 2015, at 01:39 , Sid Tantia <sid.tan...@baseboxsoftware.com> >> wrote: >> >> I tried both `nodetool remove node <Host ID>` and `nodetool decommission` >> and they both give the error: >> >> nodetool: Failed to connect to '127.0.0.1:7199' - ConnectException: >> 'Connection refused’. >> >> Here is what I have tried to fix this: >> >> 1) Uncommented JVM_OPTS=”$JVM_OPTS -Djava.rmi.server.hostname=<public >> name>” >> 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 <surbhi.gupt...@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 the cluster >>> does not use vnodes, before running the nodetool removenode command, adjust >>> the tokens. >>> >>> If the node is up, then the command would be “nodetool decommission” to >>> remove the node. >>> >>> Remove the node from the “seed list” within the configuration >>> cassandra.yaml. >>> >>> On 7 July 2015 at 12:56, Sid Tantia <sid.tan...@baseboxsoftware.com> >>> wrote: >>> >>>> Thanks for the response. I’m trying to remove a node that’s 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 <coolkiran2...@gmail.com> >>>> 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" <sid.tan...@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? >>>>>> >>>>>> >>>> >>> >> >> >
