Return-Path: 
 <commits-return-88382-apmail-cassandra-commits-archive=cassandra.apache.org@cassandra.apache.org>
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 B1F7A1084D
	for <apmail-cassandra-commits-archive@www.apache.org>;
 Fri, 20 Dec 2013 22:50:09 +0000 (UTC)
Received: (qmail 74354 invoked by uid 500); 20 Dec 2013 22:50:09 -0000
Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org
Received: (qmail 74333 invoked by uid 500); 20 Dec 2013 22:50:09 -0000
Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:commits-help@cassandra.apache.org>
List-Unsubscribe: <mailto:commits-unsubscribe@cassandra.apache.org>
List-Post: <mailto:commits@cassandra.apache.org>
List-Id: <commits.cassandra.apache.org>
Reply-To: dev@cassandra.apache.org
Delivered-To: mailing list commits@cassandra.apache.org
Received: (qmail 74324 invoked by uid 99); 20 Dec 2013 22:50:09 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 20 Dec 2013 22:50:09 +0000
Date: Fri, 20 Dec 2013 22:50:09 +0000 (UTC)
From: "Russ Hatch (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12685915.1387579697407.75273.1387579809479@arcas>
In-Reply-To: <JIRA.12685915.1387579697407@arcas>
References: <JIRA.12685915.1387579697407@arcas>
Subject: [jira] [Created] (CASSANDRA-6519) cqlsh hangs indefinitely when
 dropping table
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394

Russ Hatch created CASSANDRA-6519:
-------------------------------------

             Summary: cqlsh hangs indefinitely when dropping table
                 Key: CASSANDRA-6519
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6519
             Project: Cassandra
          Issue Type: Bug
          Components: API
         Environment: C* from trunk -- cassandra-2.0.3-709-g486f079
java 1.7.0_45 (on linux 64 bit)
[cqlsh 4.1.0 | Cassandra 2.1-SNAPSHOT | CQL spec 3.1.1 | Thrift protocol 19.39.0]

3 node cluster built on my machine using ccm
            Reporter: Russ Hatch
            Assignee: Russ Hatch


Using ccqlsh, I issue a drop statement for a table and it hangs indefinitely (running cassandra-2.0.3-709-g486f079 from trunk).

Here's the statement:
cqlsh:taskapp> drop table user_task;

Here's the full setup I used:
{noformat}
ccm create test_cluster
ccm populate -n 3
ccm start
ccm node1 cqlsh

CREATE KEYSPACE taskapp WITH replication = {
  'class': 'SimpleStrategy',
  'replication_factor': '3'
};

use taskapp;

create table user (
    user_id timeuuid PRIMARY KEY,
    first_name text,
    last_name text,
    email text
);

create table user_task (
    task_id timeuuid PRIMARY KEY,
    user_id timeuuid,
    task_order int,
    task_description text,
    is_complete boolean,
    is_top_level boolean,
    subtask_ids list<timeuuid>
);
{noformat}
and then the statement which hangs:
drop table user_task;

I also checked that all 3 nodes have the same schema version uuid, using these queries someone shared with me:
{noformat}
cqlsh:taskapp> SELECT rpc_address, schema_version FROM system.peers
           ... ;

 rpc_address | schema_version
-------------+--------------------------------------
   127.0.0.3 | 6e782241-91e9-3cfa-88c0-88f445a573c1
   127.0.0.2 | 6e782241-91e9-3cfa-88c0-88f445a573c1

(2 rows)

cqlsh:taskapp> SELECT schema_version FROM system.local WHERE key='local';

 schema_version
--------------------------------------
 6e782241-91e9-3cfa-88c0-88f445a573c1

(1 rows)
{noformat}

I checked the logs for all 3 nodes, which I think were normal. Node1 (used in the cqlsh session) showed this message:
{noformat}
INFO  [Thrift:3] 2013-12-20 14:29:23,200 MigrationManager.java:289 - Drop ColumnFamily 'taskapp/user_task'
{noformat}
The other node logs showed no activity that looked related to the attempted drop statement.



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)