cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-5064) 'Alter table' when it includes collections makes cqlsh hang
Date Thu, 13 Dec 2012 19:50:12 GMT


Sylvain Lebresne commented on CASSANDRA-5064:

Patch attached.

This is due to the fix of CASSANDRA-4786 (and it happens that this example modifies the comparator
of the CFS). The code from CASSANDRA-4786 is relying on the fact that maybeSwitchMemtable
was either returning null or was really switching the memtable. That's not the case however
if the memtable is clean (I could have swear I had checked for CASSANDRA-4786 but maybe I
missed it, or the code has changed since then). In any case, the attached patch add a 'forceSwitch'
flag to maybeSwitchMemtable that fixes the issue.
> 'Alter table' when it includes collections makes cqlsh hang
> -----------------------------------------------------------
>                 Key: CASSANDRA-5064
>                 URL:
>             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
>            Assignee: Sylvain Lebresne
>            Priority: Critical
>         Attachments: 5064.txt
> 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:

View raw message