Can't perform repair on a 1.1.5 cassandra node -SSTable corrupted

2013-08-07 Thread Madalina Matei
Hi, I have a 5 nodes cassandra (version 1.1.5) ring, RF=2, CL- READ/Write =1. After a node went down without any error reported in OS syslog or Cassandra syslog i decided to perform a repair. Each time i run a nodetool repair I get this error: INFO [FlushWriter:5] 2013-08-07 11:09:26,770 Memtab

Re: Cassandra stucks

2012-05-11 Thread Madalina Matei
in wrote: > No We are using dedicated phisical hardware. Currently we have 5 nodes. > > From: Madalina Matei [mailto:madalinaima...@gmail.com] > Sent: Friday, May 11, 2012 19:40 > To: user@cassandra.apache.org > Subject: Re: Cassandra stucks > > Are you using EC2

Re: Cassandra stucks

2012-05-11 Thread Madalina Matei
Are you using EC2 ? On 11 May 2012, at 16:13, Pavel Polushkin wrote: > We use 1.0.8 version. > > From: David Leimbach [mailto:leim...@gmail.com] > Sent: Friday, May 11, 2012 18:48 > To: user@cassandra.apache.org > Subject: Re: Cassandra stucks > > What's the version number of Cassandra? > >

Re: ebs or ephemeral

2011-10-07 Thread Madalina Matei
r > Ethernet IO performance, and it is free (included in instance price) > and the redundancy is provided by cassandra itself. > > 從我的 BlackBerry(R) 無線裝置 > -- > *From: * Madalina Matei > *Date: *Fri, 7 Oct 2011 09:02:06 +0100 > *To: * > *ReplyT

ebs or ephemeral

2011-10-07 Thread Madalina Matei
Hi, I'm looking to deploy a 5 nodes cluster in EC2 with RF3 and QUORUM CL. Could you please advice me on EBS vs ephemeral storage ? Cheers, Madalina