Mailing-List: contact dev-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Received-SPF: error (nike.apache.org: local policy)
Content-Type: text/plain; charset=iso-8859-2
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Configuration of network connectors
From: =?iso-8859-2?Q?=A3ukasz_Dywicki?= <luke@code-house.org>
In-Reply-To: <52D19973-F8B1-40DE-9A5C-5E3E96729D27@gmail.com>
Date: Tue, 9 Jul 2013 20:05:32 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <270CD5F0-0585-4117-8AE3-C02A34F15069@code-house.org>
References: <A367F3FC-F3D1-4AE0-A0D6-5E58D91BDA33@code-house.org>
 <52D19973-F8B1-40DE-9A5C-5E3E96729D27@gmail.com>
To: dev@cassandra.apache.org

Jeremy,
Sadly it does not cover our case. We have unit tests and we want to test =
really basic things like mappings of data contained in cassandra to our =
model. For that we don't need cluster at all because in unit tests we =
don't want to test data distribution. We also would like to run =
everything in JVM, thus CCM written in Python is not really what we =
need.
What we are looking for is minimal cassandra set up which could be =
embedded and used concurrently multiple times. For example we now use =
CassandraUnit:

@Rule
public CassandraUnit unit =3D new CassandraUnit(new EmptyDataSet(), =
"embedded-cassandra.yaml");

@Test
public void fistTest() {
// do something with data
}

@Test
public void secondTest() {
// do something else
}

In this set up JUnit will launch new CassandraDaemon for every test. If =
we set FORK_MODE per test then we may have two cassandra instances =
running at the same time. First test which launch CassandraDaemon will =
pass, second may fail due port usage conflict. That's why we thought =
about testing without network layer. This can save some time. It would =
be great because for some older hardware used by our developers it takes =
up to 9 minutes to run build with all unit tests. Some of this time is =
consumed by startup and shutdown of cassandra.

Cheers,
=A3ukasz Dywicki
--
luke@code-house.org
Twitter: ldywicki
Blog: http://dywicki.pl
Code-House - http://code-house.org

Wiadomo=B6=E6 napisana przez Jeremy Hanna <jeremy.hanna1234@gmail.com> w =
dniu 9 lip 2013, o godz. 15:22:

> Have you seen https://github.com/pcmanus/ccm as described in =
http://www.datastax.com/dev/blog/ccm-a-development-tool-for-creating-local=
-cassandra-clusters or does that not fit your use case?
>=20
> On 9 Jul 2013, at 14:02, =A3ukasz Dywicki <luke@code-house.org> wrote:
>=20
>> Hello,
>> First of all I would like to say hello to cassandra user and =
developer community. :)
>>=20
>> I write because we are using Cassandra in our unit tests and we have =
some troubles with network connectivity. We ca not run multiple =
cassandra instances during tests because we would need to randomize =
configuration of port and so on. For now if we try to fork our tests we =
get "address already in use" on one from two ports - native or thrift. =
In other apache projects we can "VM" connectors (ActiveMQ, Camel, Mina) =
based on in-memory queue. I took some time to see how CassandraDaemon =
starts servers and it's kinda of hardcoded. I thought about changing =
configuration to be more like:
>>=20
>> servers:
>> - class org.apache.cassandra.thrift.ThriftServer
>> - class org.apache.cassandra.transport.Server
>>=20
>> Then we will be able to disable these servers for unit tests:
>> servers:
>> - class org.apache.cassandra.vm.VmServer
>>=20
>> This requires some small changes in daemon code and client libraries. =
I'm not really deeply involved in cassandra stuff so I don't know the =
internal architecture and implications thus I look forward for you to =
discuss this topic.
>>=20
>> Cheers,
>> =A3ukasz Dywicki
>> --
>> luke@code-house.org
>> Twitter: ldywicki
>> Blog: http://dywicki.pl
>> Code-House - http://code-house.org
>>=20
>=20