[
https://issues.apache.org/jira/browse/CASSANDRA-5064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13532404#comment-13532404
]
Jonathan Ellis commented on CASSANDRA-5064:
-------------------------------------------
bq. getting the commit log context and switching the memtable is not done
atomically with respect to writes
Isn't this easily fixed by moving the context request to after the
wait-for-writes-to-finish loop?
bq. it's also possible that for postFlush tasks to not be scheduled in the
order the commit log context were acquired
Bunch of ways we could fix this, including moving switchMemtable to its own
single-threaded executor.
> '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
> Assignee: Sylvain Lebresne
> Priority: Critical
> Fix For: 1.2.0
>
> Attachments: 5064.txt, 5064-v2.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: http://www.atlassian.com/software/jira
