cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Peter Tillotson (JIRA)" <>
Subject [jira] Commented: (CASSANDRA-874) System tests against multiple nodes
Date Sat, 11 Dec 2010 23:02:02 GMT


Peter Tillotson commented on CASSANDRA-874:

I think that this may already be largely possible via a virtual network, though it presents
an ideal case. Libvirt on Linux allows you to set up virtual network interfaces on a given
host so you could get multiple instances of Cassandra running on the same local hardware,
one could probably simulate failing nodes.
see:  virsh --net-create for examples

> System tests against multiple nodes
> -----------------------------------
>                 Key: CASSANDRA-874
>                 URL:
>             Project: Cassandra
>          Issue Type: Test
>          Components: Tools
>            Reporter: Jonathan Ellis
> We have a system test suite (see ) but
it only runs against the local machine, which is suboptimal even if we didn't have a bunch
of optimizations to make writes to a local node skip most of the messaging layer.
> We'd like to automate testing against a whole cluster.  Paul has some code using libcloud
to do stress tests against an ephemeral rackspace cloud servers cluster at,
which is probably useful as a starting point, but rather than running you'd want
to put together a more comprehensive suite, based on the existing system tests but also explicitly
covering things like range queries that span multiple nodes and failure conditions like Hinted
Handoff (see ) and repair (
) resulting from deliberately disabling a node temporarily.
> Adding tests for ops tasks like would be
awesome too.
> Finally, CASSANDRA-561 might make something like this possible using a simulator instead
of hardware-level virtualization, which would be both more convenient and less expensive.
 But someone just dumped a huge zip in our laps w/o really trying to collaborate with us there,
so if you want to try to resurrect that code or otherwise go that route, be more open about
what you're doing. :)

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message