[jira] [Comment Edited] (CASSANDRA-5460) Consistency issue with CL.TWO

["Ryan McGuire (JIRA)" <ji...@apache.org>]

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

Ryan McGuire edited comment on CASSANDRA-5460 at 8/13/14 9:18 PM:
------------------------------------------------------------------

A few notes:

 * It seems like this test suite is getting a lot of copy and pasting. Looks like we can condense most of these down to a single helper test that takes the write and read CLs as arguments and then each test just calls the helper test.
 * There's several more CLs that we aren't testing, particularly multi-datacenter (LOCAL_QUORUM, EACH_QUORUM) (see http://www.datastax.com/documentation/cassandra/2.0/cassandra/dml/dml_config_consistency_c.html)
 * These tests may be too basic to stress test what [~tjake] was seeing, as I doubt he was having problems reading with a mostly idle cluster.


was (Author: enigmacurry):
A few notes:

 * It seems like this test suite is getting a lot of copy and pasting. Looks like we can condense most of these down to a single helper test that takes the write and read CLs and then each test just calls the helper test.
 * There's several more CLs that we aren't testing, particularly multi-datacenter (LOCAL_QUORUM, EACH_QUORUM) (see http://www.datastax.com/documentation/cassandra/2.0/cassandra/dml/dml_config_consistency_c.html)
 * These tests may be too basic to stress test what [~tjake] was seeing, as I doubt he was having problems reading with a mostly idle cluster.

> Consistency issue with CL.TWO
> -----------------------------
>
>                 Key: CASSANDRA-5460
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5460
>             Project: Cassandra
>          Issue Type: Test
>    Affects Versions: 1.2.0
>            Reporter: T Jake Luciani
>            Assignee: Philip Thompson
>            Priority: Minor
>
> We have a keyspace with RF=4.  We write at QUORUM and read at TWO.  This should provide consistency since writes are on 3 replicas and we read from 2, but in practice we don't have consistent reads.



--
This message was sent by Atlassian JIRA
(v6.2#6252)