Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (athena.apache.org: domain of driftx@gmail.com designates
 209.85.214.44 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAC43XBmUayqT_tkhFwht9cx9Wa3DxeQsD4gZwtLyT8DSpQFFPQ@mail.gmail.com>
References: 
 <CAC43XBmUayqT_tkhFwht9cx9Wa3DxeQsD4gZwtLyT8DSpQFFPQ@mail.gmail.com>
From: Brandon Williams <driftx@gmail.com>
Date: Wed, 9 Nov 2011 06:01:35 -0600
Message-ID: 
 <CAAafH9Ts+E75zz_SKh4t_1P3YvBHZX+BGyekU81sZuQ8CQbvgQ@mail.gmail.com>
Subject: Re: decommissioned node still in "LoadMap" in JMX Management Console
To: user@cassandra.apache.org
Content-Type: text/plain; charset=ISO-8859-1

On Wed, Nov 9, 2011 at 1:28 AM, Patrik Modesto <patrik.modesto@gmail.com> wrote:
> Hi,
>
> on our production cluster of 8 nodes which is running cassandra 0.8.7
> we still see in the MBean
> "org.apache.cassandra.db:type=StorageService.LoadMap" in JMX
> Management console the 9th node we added for testing for a short time.
> After the testing we decommissioned the 9th node and has been
> reinstalled for another use. The node is not reported by `nodetool
> ring` not is it in
> "org.apache.cassandra.db:type=StorageService.LiveNodes" MBean.
>
> Is it a feature or a bug?

Appears to be a minor bug: https://issues.apache.org/jira/browse/CASSANDRA-3475

-Brandon