Hmm...I've tried changing my column family name to "MySchema" instead. Now the cli is behaving normally, but the OOM error still occurs when I get_range_slices from my code.
From: Stephen Pope [mailto:stephen.p...@quest.com] Sent: Thursday, August 25, 2011 11:10 AM To: user@cassandra.apache.org Subject: Column Family names Using 0.8.2, I've created a column family called "_Schema" (without the quotes). For some reason, I can't seem to list the rows in it from the cli: I've tried: [default@BIM] list _Schema; Syntax error at position 5: unexpected "_" for `list _Schema;`. [default@BIM] list '_Schema'; Syntax error at position 5: mismatched input ''_Schema'' expecting Identifier [default@BIM] list "_Schema"; Syntax error at position 5: unexpected """ for `list "_Schema";`. Am I doing something wrong? Also, after creating the (empty) column family, I then try to read the entire column family using get_range_slices. I'm using an empty byte array for the start key (and start column), and a byte array containing '\uffff' for the end key (and end column). When I do this, Cassandra throws this: java.lang.OutOfMemoryError: Java heap space Dumping heap to java_pid2508.hprof ... Heap dump file created [5211347 bytes in 0.100 secs] ERROR 10:44:07,543 Internal error processing get_range_slices java.lang.OutOfMemoryError: Java heap space at java.util.ArrayList.<init>(ArrayList.java:112) at org.apache.cassandra.service.StorageProxy.getRangeSlice(StorageProxy. java:670) at org.apache.cassandra.thrift.CassandraServer.get_range_slices(Cassandr aServer.java:617) at org.apache.cassandra.thrift.Cassandra$Processor$get_range_slices.proc ess(Cassandra.java:3202) at org.apache.cassandra.thrift.Cassandra$Processor.process(Cassandra.jav a:2889) at org.apache.cassandra.thrift.CustomTThreadPoolServer$WorkerProcess.run (CustomTThreadPoolServer.java:187) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExec utor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor .java:908) at java.lang.Thread.run(Thread.java:662) Even though I've got 8GB of ram in my machine, and the java process is only using 92MB of memory. Has anyone seen this before? Cheers, Steve
