This is running the Amazon Linux OS which is essentially CentOS 6 I believe.
java version "1.6.0_45" Java(TM) SE Runtime Environment (build 1.6.0_45-b06) Java HotSpot(TM) 64-Bit Server VM (build 20.45-b01, mixed mode) Installed cassandra 1.2.9 from http://archive.apache.org/dist/cassandra/1.2.9/apache-cassandra-1.2.9-bin.tar.gzthen tar -xzf to a directory, change the .yaml file a bit (using vnodes, set concurrent_writes to 16) change the cassandra-env.sh changed MAX_HEAP_SIZE to 3G and HEAP_NEWSIZE=200M On Tue, Dec 3, 2013 at 12:05 PM, Robert Coli <rc...@eventbrite.com> wrote: > On Tue, Dec 3, 2013 at 6:19 AM, John Pyeatt <john.pye...@singlewire.com>wrote: > >> Then my issue must be the 0.000001% because >> >> 1) I'm running the repair as root. >> > > Huh? Repair doesn't care what user your shell is. It is a process built > into cassandra and has the permissions that cassandra does? > > >> 2) The directory exists and the permissions are appropriate. root:root 755 >> > > Why are you running Cassandra as root? > > >> 3) The three times it occurred during the repair it always complained >> about backups directories. But there are dozens other backups directories >> that were created during the repair that caused no exceptions. >> > > Cassandra doesn't have a lot of chances to mess up while creating > directories. This appears to be one of them. > > >> The biggest issue with this is that is shuts down gossip. >> > > That sounds like rather a serious issue, and hints towards a potential > common cause : too many open files? > > To rule out other potential causes of issue : > > - what o/s? > - what JVM? > - how have you installed cassandra? > - what version of cassandra? > > =Rob > -- John Pyeatt Singlewire Software, LLC www.singlewire.com ------------------ 608.661.1184 john.pye...@singlewire.com
