You should upgrade before wasting time troubleshooting such an old install.
On Thu, Feb 24, 2011 at 8:45 AM, Tomer B <tomer...@gmail.com> wrote: > Hi > i'm using a 3 node cluster of cassandra 0.6.1 together with hector as api to > java client. > every few days I get a situation where I cannot connect to cassandra, other > than that the data dir is filling up the whole disk space and the > synchronization stops at these times, the exceptions I get are as following: > Happended 3386 in 24H: POOL EXHAUSTED: 02:00:30.225 [MyThread[5]]: Unable to > connect to cassandra node xxx.xx.xx.32:9160 will try the next node, Pool > exhausted > Happened 6848 in 24H CONNECTION REFUSED: 06:14:48.598 [MyThread[4]]: Unable > to connect to cassandra node xxx.xx.xx.30:9160 will try the next node, > Unable to open transport to xxx.xx.xx.30:9160 , java.net.ConnectException: > Connection refused: connect > Happened 84 times in 24H: NULL OUTPUTSTREAM: 06:14:48.504 [MyThread[2]]: > async execution fail, Cannot write to null outputStream > Happened 14 times in 24H: CONNECTION TIMED OUT: 06:15:08.019 [MyThread[0]]: > Unable to connect to cassandra node xxx.xx.xx.31:9160 will try the next > node, Unable to open transp ort to xxx.xx.xx.31:9160 , > java.net.ConnectException: Connection timed out: connect > Can anyone assist or suggest what could be the problem? note that the node > is funcioning well and it happens once every few days. > -- Jonathan Ellis Project Chair, Apache Cassandra co-founder of DataStax, the source for professional Cassandra support http://www.datastax.com
