On 28 Sep 2010, at 08:37, Michael Dürgner wrote:
>> What do you mean by "running live"? I am also planning to use cassandra on
>> EC2 using small nodes. Small nodes have 1/4 cpu of the large ones, 1/4 cost,
>> but I/O is more than 1/4 (amazon does not give explicit I/O numbers...), so
>> I thi
Sent from my iPhone
On 27.09.2010, at 19:30, Marc Canaleta wrote:
> What do you mean by "running live"? I am also planning to use cassandra on
> EC2 using small nodes. Small nodes have 1/4 cpu of the large ones, 1/4 cost,
> but I/O is more than 1/4 (amazon does not give explicit I/O numbers.
> What do you mean by "running live"? I am also planning to use cassandra on
I believe live as in "in production".
> EC2 using small nodes. Small nodes have 1/4 cpu of the large ones, 1/4 cost,
> but I/O is more than 1/4 (amazon does not give explicit I/O numbers...), so
> I think 4 small instanc
What do you mean by "running live"? I am also planning to use cassandra on
EC2 using small nodes. Small nodes have 1/4 cpu of the large ones, 1/4 cost,
but I/O is more than 1/4 (amazon does not give explicit I/O numbers...), so
I think 4 small instances should perform better than 1 large one (and t
I strongly recommend not running live on Small nodes. So in your case
I would recommend starting up Large instances with raid0'd disks, shut
down cassandra on the Small ones, rsync to the Large, and start up on
Large.
On Mon, Sep 27, 2010 at 6:46 AM, Utku Can Topçu wrote:
> Hi All,
>
> We're cur
Hi All,
We're currently running a cassandra cluster with Replication Factor 3,
consisting of 4 nodes.
The current situation is:
- The nodes are all identical (AWS small instances)
- Data directory is in the partition (/mnt) which has 150G capacity and each
node has around 90 GB load, so 60 G fre
