[
https://issues.apache.org/jira/browse/CASSANDRA-9851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Knighton updated CASSANDRA-9851:
-------------------------------------
Description:
Reproducible as of a66863861136a29dc04d7bc3b319f9f8fae0f49f on trunk, as well
as in other recent commits.
Durability of writes seems to be violated, even under batch commitlog mode.
This issue was discovered by a test that adds a range of values to a CQL Set,
with no deletes issued. The test is available here
https://github.com/riptano/jepsen/blob/cassandra/cassandra/src/cassandra/collections/set.clj#L56.
During this write pattern, random nodes in the 5 node cluster are kill -9ed.
Once all nodes have been brought back up, another read at CL.ALL is issued.
This read fails to return values that have previously been successfully read
from the cluster. This problem is not reproducible on 2.1.* or 2.2.
Log files from each node are attached.
was:
Reproducible as of a66863861136a29dc04d7bc3b319f9f8fae0f49f on trunk, as well
as in other recent commits.
Durability of writes seems to be violated, even under batch commitlog mode.
This issue was discovered by a test that adds a range of values to a CQL Set,
with no deletes issued. The test is available here
https://github.com/riptano/jepsen/blob/cassandra/cassandra/src/cassandra/collections/set.clj#L56.
A read is then issued with consistency level ALL.
During this write pattern, random nodes in the cluster are kill -9ed. Once all
nodes have been brought back up, another read is issued. This read fails to
return values that have previously been successfully read from the cluster.
This problem is not reproducible on 2.1.* or 2.2.
Log files from each node are attached.
> Write Durability Failures Even During Batch Commit Mode
> --------------------------------------------------------
>
> Key: CASSANDRA-9851
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9851
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Environment: Debian, x86_64, Kernel 3.16.7
> Reporter: Joel Knighton
> Attachments: n1.log, n2.log, n3.log, n4.log, n5.log
>
>
> Reproducible as of a66863861136a29dc04d7bc3b319f9f8fae0f49f on trunk, as well
> as in other recent commits.
> Durability of writes seems to be violated, even under batch commitlog mode.
> This issue was discovered by a test that adds a range of values to a CQL Set,
> with no deletes issued. The test is available here
> https://github.com/riptano/jepsen/blob/cassandra/cassandra/src/cassandra/collections/set.clj#L56.
> During this write pattern, random nodes in the 5 node cluster are kill -9ed.
> Once all nodes have been brought back up, another read at CL.ALL is issued.
> This read fails to return values that have previously been successfully read
> from the cluster. This problem is not reproducible on 2.1.* or 2.2.
> Log files from each node are attached.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
