Return-Path: X-Original-To: apmail-cassandra-commits-archive@www.apache.org Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3CE43FB59 for ; Fri, 12 Dec 2014 17:30:14 +0000 (UTC) Received: (qmail 98922 invoked by uid 500); 12 Dec 2014 17:30:13 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 98881 invoked by uid 500); 12 Dec 2014 17:30:13 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 98869 invoked by uid 99); 12 Dec 2014 17:30:13 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 12 Dec 2014 17:30:13 +0000 Date: Fri, 12 Dec 2014 17:30:13 +0000 (UTC) From: "Brandon Williams (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CASSANDRA-8428) Nodetool Drain kills C* Process MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CASSANDRA-8428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14244474#comment-14244474 ] Brandon Williams commented on CASSANDRA-8428: --------------------------------------------- I mean drain has never exited, and still should not. It's the write error and stop policy that's killing it, not drain. > Nodetool Drain kills C* Process > ------------------------------- > > Key: CASSANDRA-8428 > URL: https://issues.apache.org/jira/browse/CASSANDRA-8428 > Project: Cassandra > Issue Type: Bug > Reporter: Philip Thompson > Assignee: Brandon Williams > Labels: nodetool > Fix For: 2.0.12 > > Attachments: system.log > > > Nodetool Drain is documented at http://wiki.apache.org/cassandra/NodeTool and in the nodetool help to flush a node and stop accepting writes. This is the behavior I see with 2.1.2. > In 2.0.11 and 1.2.19, instead the Cassandra Process is killed. In the 1.2.19 logs, I see: > {code} > INFO [RMI TCP Connection(2)-192.168.1.5] 2014-12-05 10:32:44,234 StorageService.java (line 964) > DRAINING: starting drain process > INFO [RMI TCP Connection(2)-192.168.1.5] 2014-12-05 10:32:44,235 ThriftServer.java (line 116) S > top listening to thrift clients > INFO [RMI TCP Connection(2)-192.168.1.5] 2014-12-05 10:32:44,239 Server.java (line 159) Stop li > stening for CQL clients > INFO [RMI TCP Connection(2)-192.168.1.5] 2014-12-05 10:32:44,239 Gossiper.java (line 1203) Announcing shutdown > INFO [RMI TCP Connection(2)-192.168.1.5] 2014-12-05 10:32:46,240 MessagingService.java (line 696) Waiting for messaging service to quiesce > INFO [ACCEPT-/127.0.0.1] 2014-12-05 10:32:46,241 MessagingService.java (line 919) MessagingService shutting down server thread.{code} > So it appears this in an intentional shut down, in which case the docs and help are wrong. I could not find a JIRA that described the change in behavior moving to 2.1. > Other users on IRC report that drain works as expected for them on 1.2.19. Attached are 2.0 logs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)