Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Fri, 24 Apr 2015 00:06:38 +0000 (UTC)
From: "Jonathan Ellis (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12787733.1427993558000.12938.1429833998773@Atlassian.JIRA>
In-Reply-To: <JIRA.12787733.1427993558000@Atlassian.JIRA>
References: <JIRA.12787733.1427993558000@Atlassian.JIRA>
 <JIRA.12787733.1427993558335@arcas>
Subject: [jira] [Commented] (CASSANDRA-9100) Gossip is inadequately tested
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jonathan Ellis commented on CASSANDRA-9100:
-------------------------------------------

[~jasobrown] is it worth trying to make gossip testable, before ripping it apart?

> Gossip is inadequately tested
> -----------------------------
>
>                 Key: CASSANDRA-9100
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9100
>             Project: Cassandra
>          Issue Type: Test
>          Components: Core
>            Reporter: Ariel Weisberg
>
> We found a few unit tests, but nothing that exercises Gossip under challenging conditions. Maybe consider a long test that hooks up some gossipers over a fake network and then do fault injection on that fake network. Uni-directional and bi-directional partitions, delayed delivery, out of order delivery if that is something that they can see in practice. Connects/disconnects.
> Also play with bad clocks.


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