Removal of nodes does not reflect in cmon cluster overview

Bug #368948 reported by Phil Bayfield on 2009-04-29
2
Affects Status Importance Assigned to Milestone
cmon
Undecided
johan

Bug Description

I removed some unwanted MYSQLD nodes from my cluster today.
Cmon still shows the removed nodes:

5 192.168.10.4 CONNECTED 6.3.24 2009-04-29 00:24:52
6 192.168.10.4 CONNECTED 6.3.24 2009-04-29 00:24:52
7 192.168.10.4 CONNECTED 6.3.24 2009-04-29 00:24:52
8 192.168.10.5 CONNECTED 6.3.24 2009-04-29 00:24:52
9 192.168.10.5 CONNECTED 6.3.24 2009-04-29 00:24:52
10 192.168.10.5 CONNECTED 6.3.24 2009-04-29 00:24:52
11 192.168.10.4 CONNECTED 6.3.24 2009-04-29 00:24:52
12 0.0.0.0 Accepting connections 2009-04-29 00:24:52
13 0.0.0.0 Accepting connections 2009-04-29 00:24:52
14 0.0.0.0 Accepting connections 2009-04-28 18:31:58
15 0.0.0.0 Accepting connections 2009-04-28 18:31:58
16 0.0.0.0 Accepting connections 2009-04-28 18:31:58
17 0.0.0.0 Accepting connections 2009-04-28 18:31:58

However the actual cluster nodes are:

[mysqld(API)] 9 node(s)
id=5 @192.168.10.4 (mysql-5.1.32 ndb-6.3.24)
id=6 @192.168.10.4 (mysql-5.1.32 ndb-6.3.24)
id=7 @192.168.10.4 (mysql-5.1.32 ndb-6.3.24)
id=8 @192.168.10.5 (mysql-5.1.32 ndb-6.3.24)
id=9 @192.168.10.5 (mysql-5.1.32 ndb-6.3.24)
id=10 @192.168.10.5 (mysql-5.1.32 ndb-6.3.24)
id=11 @192.168.10.4 (mysql-5.1.32 ndb-6.3.24)
id=12 (not connected, accepting connect from 192.168.10.6)
id=13 (not connected, accepting connect from 192.168.10.7)

Hi,

Thanks a lot for this report - I will see what I can do about it.
It is actually (in a nice way) tricky to find out if nodes has been
removed.

BR

johan

Phil Bayfield wrote:
> Public bug reported:
>
> I removed some unwanted MYSQLD nodes from my cluster today.
> Cmon still shows the removed nodes:
>
> 5 192.168.10.4 CONNECTED 6.3.24 2009-04-29 00:24:52
> 6 192.168.10.4 CONNECTED 6.3.24 2009-04-29 00:24:52
> 7 192.168.10.4 CONNECTED 6.3.24 2009-04-29 00:24:52
> 8 192.168.10.5 CONNECTED 6.3.24 2009-04-29 00:24:52
> 9 192.168.10.5 CONNECTED 6.3.24 2009-04-29 00:24:52
> 10 192.168.10.5 CONNECTED 6.3.24 2009-04-29 00:24:52
> 11 192.168.10.4 CONNECTED 6.3.24 2009-04-29 00:24:52
> 12 0.0.0.0 Accepting connections 2009-04-29 00:24:52
> 13 0.0.0.0 Accepting connections 2009-04-29 00:24:52
> 14 0.0.0.0 Accepting connections 2009-04-28 18:31:58
> 15 0.0.0.0 Accepting connections 2009-04-28 18:31:58
> 16 0.0.0.0 Accepting connections 2009-04-28 18:31:58
> 17 0.0.0.0 Accepting connections 2009-04-28 18:31:58
>
> However the actual cluster nodes are:
>
> [mysqld(API)] 9 node(s)
> id=5 @192.168.10.4 (mysql-5.1.32 ndb-6.3.24)
> id=6 @192.168.10.4 (mysql-5.1.32 ndb-6.3.24)
> id=7 @192.168.10.4 (mysql-5.1.32 ndb-6.3.24)
> id=8 @192.168.10.5 (mysql-5.1.32 ndb-6.3.24)
> id=9 @192.168.10.5 (mysql-5.1.32 ndb-6.3.24)
> id=10 @192.168.10.5 (mysql-5.1.32 ndb-6.3.24)
> id=11 @192.168.10.4 (mysql-5.1.32 ndb-6.3.24)
> id=12 (not connected, accepting connect from 192.168.10.6)
> id=13 (not connected, accepting connect from 192.168.10.7)
>
> ** Affects: cmon
> Importance: Undecided
> Status: New
>
>

johan (johan-severalnines) wrote :

will be in cmon 0.15.

-j

Changed in cmon:
assignee: nobody → johan (johan-severalnines)
status: New → Fix Committed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers