Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Tue, 6 Jan 2015 23:21:34 +0000 (UTC)
From: "Jonathan Ellis (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12764541.1420216781000.23831.1420586494967@Atlassian.JIRA>
In-Reply-To: <JIRA.12764541.1420216781000@Atlassian.JIRA>
References: <JIRA.12764541.1420216781000@Atlassian.JIRA>
 <JIRA.12764541.1420216781718@arcas>
Subject: [jira] [Commented] (CASSANDRA-8554) Node where gossip is disabled
 still shows  as UP on that node; other nodes show it as DN
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CASSANDRA-8554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14266948#comment-14266948 ] 

Jonathan Ellis commented on CASSANDRA-8554:
-------------------------------------------

Gossip is hardcoded to think "of course I'm alive, or I wouldn't be answering questions about whether I'm alive."  Should be simple to add a check for drain-status.

> Node where gossip is disabled still shows  as UP on that node; other nodes show it as DN
> ----------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-8554
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8554
>             Project: Cassandra
>          Issue Type: Bug
>         Environment: Centos 6.5, DSE4.5.1 tarball install
>            Reporter: Mark Curtis
>            Priority: Minor
>
> When running nodetool drain, the drained node will still show the status of itself as UP in nodetool status even after the drain has finished. For example using a 3 node cluster on one of the nodes that is still operating and not drained we see this:
> {code}
> $ ./dse-4.5.1/bin/nodetool status
> Note: Ownership information does not include topology; for complete information, specify a keyspace
> Datacenter: Central
> ===================
> Status=Up/Down
> |/ State=Normal/Leaving/Joining/Moving
> --  Address        Load       Tokens  Owns   Host ID                               Rack
> UN  192.168.56.21  210.78 KB  256     32.1%  82eb2fca-4f57-467b-a972-93096ec5d69f  RAC1
> DN  192.168.56.23  2.22 GB    256     33.5%  a11bfac1-fad0-440b-bd68-7562a89ce3c7  RAC1
> UN  192.168.56.22  2.22 GB    256     34.4%  4250cb05-97be-4bac-887a-acc307d1bc0c  RAC1
> {code}
> While on the drained node we see this:
> {code}
> [datastax@DSE4 ~]$ ./dse-4.5.1/bin/nodetool drain
> [datastax@DSE4 ~]$ ./dse-4.5.1/bin/nodetool status
> Note: Ownership information does not include topology; for complete information, specify a keyspace
> Datacenter: Central
> ===================
> Status=Up/Down
> |/ State=Normal/Leaving/Joining/Moving
> --  Address        Load       Tokens  Owns   Host ID                               Rack
> UN  192.168.56.21  210.78 KB  256     32.1%  82eb2fca-4f57-467b-a972-93096ec5d69f  RAC1
> UN  192.168.56.23  2.22 GB    256     33.5%  a11bfac1-fad0-440b-bd68-7562a89ce3c7  RAC1
> UN  192.168.56.22  2.22 GB    256     34.4%  4250cb05-97be-4bac-887a-acc307d1bc0c  RAC1
> {code}
> Netstat shows outgoing connections from the drained node to other nodes as still established on port 7000 but the node is no longer listening on port 7000 which I believe is expected.
> However the output of nodetool status on the drained node could be interpreted as misleading.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)