Out of memory issues

SIZE="200M" This is the complete error log http://pastebin.com/QGaACyhR This is cassandra_env http://pastebin.com/6SLeVmtv This is cassandra.yaml http://pastebin.com/wb1axHtV Can anyone help? Regards, Paolo Crosato -- Paolo Crosato Software engineer/Custom Solutions e-mail: paolo.cros...@targaubiest.com

Re: Out of memory issues

com/QGaACyhR This is cassandra_env http://pastebin.com/6SLeVmtv This is cassandra.yaml http://pastebin.com/wb1axHtV Can anyone help? Regards, Paolo Crosato -- Paolo Crosato Software engineer/Custom Solutions e-mail:paolo.cros...@targaubiest.com <mailto

RE: hardware sizing for cassandra

s and 16 gb or ram, 32 is rarely needed and 64 a waste. 8 cores would probably be too much with 1000 writes a second. Paolo Paolo Crosato Software engineer/Custom Solu

CF performance suddenly degraded

ed nothing on the application level since days, so it's not something related to the applicacation or the driver. Is there anyway I can troubleshoot the issue and discover what's making the table so slow? Thanks for any advice, Paolo -- Paolo Crosato Software engineer/Cus

nodetool repair stalled

18]) Has anybody any suggestion on why a nodetool repair might be stuck and how to debug it? Regards, Paolo Crosato

Re: nodetool repair stalled

.jar:/usr/share/cassandra/lib/stress.jar:/usr/share/cassandra/lib/thrift-server-0.3.2.jar -Xmx32m -Dlog4j.configuration=log4j-tools.properties -Dstorage-config=/etc/cassandra/conf org.apache.cassandra.tools.NodeCmd -p 7199 repair tiergast positions Is this a known bug? Regards, Paolo Crosato

Best practices for repair

practices for repairs or if there is some other option that makes repair easier to perform, and more reliable that it is now. Regards, Paolo Crosato -- Paolo Crosato Software engineer/Custom Solutions e-mail: paolo.cros...@targaubiest.com

Re: Best practices for repair

tation/cassandra/2.0/cassandra/operations/ops_repair_nodes_c.html If you or anybody else finds it inadequate, speak up. -- Jack Krupansky -Original Message----- From: Paolo Crosato Sent: Thursday, June 19, 2014 10:13 AM To: user@cassandra.apache.org <mailto:user@c

Issue with source command and utf8 file

le, Ô is encoded as C394. When I try to load the file I get this error: cqlsh:demodb> source 'rhone.cql'; rhone.cql:3:Incomplete statement at end of file The error disappears only when I remove all the non ascii characters. If I copy and paste the insert on cqlsh shell, it works. Cassandra is installed on a centos 6.3 server, LANG is .UTF8, I tried connecting from remote both with gnome terminal and putty on windows, with utf-8 shell, no success on both. Has anybody got any clue? Regards, Paolo -- Paolo Crosato Software engineer/Custom Solutions

Problem with sstableloader from text data

} positionsWriter.addColumn(bytes("status"), bytes(status), timestamp); positionsWriter.addColumn(bytes("value"), bytes(line), timestamp); System.out.println("line: "+line); } reader.close(); position