[jira] [Comment Edited] (CASSANDRA-5064) 'Alter table' when it includes collections makes cqlsh hang

["Brandon Williams (JIRA)" <ji...@apache.org>]

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

Brandon Williams edited comment on CASSANDRA-5064 at 12/13/12 6:11 PM:
-----------------------------------------------------------------------

Repros on trunk as well.  Jstack indicates the commit log writer and memtable post flusher are consuming most of the cpu. Affects the entire cluster.
                
      was (Author: brandon.williams):
    Repros on trunk as well.  Jstack indicates the commit log writer and memtable post flusher are consuming most of the cpu.
                  
> 'Alter table' when it includes collections makes cqlsh hang
> -----------------------------------------------------------
>
>                 Key: CASSANDRA-5064
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5064
>             Project: Cassandra
>          Issue Type: Bug
>    Affects Versions: 1.2.0 beta 3, 1.2.0
>         Environment: Ubuntu 12.04 LTS
> 3.2.0-23-virtual
>            Reporter: Ryan McGuire
>            Priority: Critical
>
> Having just installed 1.2.0-beta3 issue the following CQL into cqlsh:
> {code}
> drop keyspace test;
> create keyspace test with replication = {
>           'class': 'SimpleStrategy',
>           'replication_factor': '1'
>         };
> use test;
> create table users (
>             user_id text PRIMARY KEY,
>             first_name text,
>             last_name text,
>             email_addresses set<text>
>         );
> alter table users add mailing_address_lines list<text>;
> {code}
> As soon as you issue the alter table statement cqlsh hangs, and the java process hosting Cassandra consumes 100% of a single core's CPU.
> If the alter table doesn't include a collection, it runs fine.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira