As Ryan said, Cassandra's really designed to manage DAS. That's probably a big part of the problem.
If you have to use a SAN, I recommend checking out this thread: http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Cassandra-on-iSCSI-td5945217.html On Tue, Jun 14, 2011 at 8:16 AM, Schuilenga, Jan Taeke <jantaeke.schuile...@ocwduo.nl> wrote: > Hi All, > > We are having issues testing Cassandra in a virtualized environment (Vmware > ESX). > Our challenge is to combine a high number of concurrent users with a very > low maximum response time. > Immediately we ran into a problem with scalability where our performance > (Trx per sec) unexpectedly degrades after adding nodes without > overcommitting host cpu resources too much as far as we can tell. > > Therefore we are looking for bestpractices or anybody with experiences with > cassandra in a similar environment to help us. > > So far we only found the following article which hasn’t helped so far: > http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Node-added-no-performance-boost-are-the-tokens-correct-td6228872.html > > Our current test setup using the java version of the cassandra load tool > consists of: > Hardware: Vmware ESX cluster with IBM 3850 (4x dual core cpu) Hosts on > Compellent FC SAN for storage > Cassandra: 3-6 node 2vCpu Centos guest boxes (RF=2) > > Jan-Taeke Schuilenga -- Jonathan Ellis Project Chair, Apache Cassandra co-founder of DataStax, the source for professional Cassandra support http://www.datastax.com
