cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon Williams (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-6144) Schema torture test
Date Thu, 10 Oct 2013 22:42:42 GMT

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

Brandon Williams commented on CASSANDRA-6144:
---------------------------------------------

In the spirit of CASSANDRA-6177, I would recommend not sleeping and instead poll the schema
for completeness.  Also it looks like concurrent_schema_changes_test.py does something fairly
similar to this, so it's probably at least worth looking at.

> Schema torture test
> -------------------
>
>                 Key: CASSANDRA-6144
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6144
>             Project: Cassandra
>          Issue Type: Test
>            Reporter: Daniel Meyer
>            Assignee: Daniel Meyer
>
> Develop schema torture tests for running in both dtest as well as against a distributed
cluster.
> Torture test will include repeated cycle of *concurrent* create, alter, drop, truncate,
etc.
> Run torture test against variable size clusters in case schema disagreements occur more
frequently with more nodes.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message