You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Brandon Williams (JIRA)" <ji...@apache.org> on 2013/10/08 22:04:45 UTC
[jira] [Reopened] (CASSANDRA-6154) Inserts are blocked in 2.1
[ https://issues.apache.org/jira/browse/CASSANDRA-6154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brandon Williams reopened CASSANDRA-6154:
-----------------------------------------
Actually, there's something wrong in the 2.0 branch that points at this commit too, but it's harder to trigger. Using a batch such as:
{noformat}
BEGIN BATCH
INSERT INTO users (id, firstname, lastname) VALUES (0, 'Jack', 'Sparrow')
INSERT INTO users (id, firstname, lastname) VALUES (1, 'Will', 'Turner')
APPLY BATCH
{noformat}
at ONE with 2 of 3 nodes down should timeout, but never returns.
> Inserts are blocked in 2.1
> --------------------------
>
> Key: CASSANDRA-6154
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6154
> Project: Cassandra
> Issue Type: Bug
> Reporter: Ryan McGuire
> Assignee: Jonathan Ellis
> Priority: Critical
> Attachments: 6154.txt, 6154-v2.txt
>
>
> With cluster sizes >1 inserts are blocked indefinitely:
> {code}
> $ ccm create -v git:trunk test
> Fetching Cassandra updates...
> Current cluster is now: test
> $ ccm populate -n 2
> $ ccm start
> $ ccm node1 cqlsh
> Connected to test at 127.0.0.1:9160.
> [cqlsh 4.0.1 | Cassandra 2.1-SNAPSHOT | CQL spec 3.1.1 | Thrift protocol 19.37.0]
> Use HELP for help.
> cqlsh> CREATE KEYSPACE timeline WITH replication = {'class': 'SimpleStrategy', 'replication_factor': 1};
> cqlsh> USE timeline;
> cqlsh:timeline> CREATE TABLE user_events (userid text, event timestamp, value text, PRIMARY KEY (userid, event));
> cqlsh:timeline> INSERT INTO user_events (userid, event , value ) VALUES ( 'ryan', '2013-10-07', 'attempt');
> {code}
> The last INSERT statement never returns..
--
This message was sent by Atlassian JIRA
(v6.1#6144)