Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Mon, 4 Apr 2016 09:36:25 +0000 (UTC)
From: "Prashanth (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12955713.1459762552000.124304.1459762585433@Atlassian.JIRA>
In-Reply-To: <JIRA.12955713.1459762552000@Atlassian.JIRA>
References: <JIRA.12955713.1459762552000@Atlassian.JIRA>
 <JIRA.12955713.1459762552321@arcas>
Subject: [jira] [Created] (CASSANDRA-11484) Consistency issues with
 subsequent writes, deletes and reads
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Prashanth created CASSANDRA-11484:
-------------------------------------

             Summary: Consistency issues with subsequent writes, deletes and reads
                 Key: CASSANDRA-11484
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11484
             Project: Cassandra
          Issue Type: Bug
         Environment: Cassandra version: DataStax Enterprise 4.7.1
Driver version: cassandra-driver-core-2.1.7.1
            Reporter: Prashanth
         Attachments: CassandraDbCheckAppTest.java

There have been intermittent failures when the following subsequent queries are performed on a 4 node cluster:
1. Insert a few records with consistency level QUORUM
2. Delete one of the records with consistency level ALL
3. Retrieve all the records with consistency level QUORUM or ALL and test that the deleted record does not exist

The tests are failing because the record does not appear to be deleted and a pattern for the failures couldn't be established.

A snippet of the code is attached to this issue so that the setup/tear down mechanism can be seen as well. 
(Both truncating and dropping the table approaches where used as a tear down mechanism)


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)