incubator-cassandra-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nathan McCall <n...@vervewireless.com>
Subject Re: Embedded integration testing causing strage issues
Date Fri, 13 Aug 2010 04:24:29 GMT
Do you have a test case you can put up somewhere that triggers this? I
have not had this issue, but I don't think we test with any more than
100 rows at most for any given unit test.

On Thu, Aug 12, 2010 at 6:59 PM, Todd Nine <todd@spidertracks.co.nz> wrote:
> Hi all,
>  We've downloaded and used Ran's embedded Cassandra helper from the
> Hector client.  It works really well for performing basic integration
> testing.  We have a more advanced test that uses TCP sockets and
> threading.  We send about 400 pieces of data via TCP.  This results in
> ~1200 writes and ~800 reads in our embedded Cassandra over 15 seconds.
> Occasionally, the test will fail due to less than the 400 packets of
> data being written, though the calling client code receives no errors
> from Cassandra on the writes.  We see this behavior more on dual
> processor systems over quad core systems.  If we change the tests to use
> Cassandra running on it's own, the issues seem to disappear regardless
> of the system size.
>
> This isn't a stress test, just a simple test with a very small input
> set.  Is it possible to tweak any of the storage-conf.xml settings to
> make the embedded test instance more reliable?  We don't need high
> throughput only reliability to test our code and the results in simple
> integration tests.
>
> Version 0.6.3
>
> Thanks,
> Todd
>

Mime
View raw message