Re: java.util.concurrent.TimeoutException: Operation timed out - received only 0 responses from .

2009-12-05 Thread mobiledreamers
i use a 64 bit machine and gave 6gigs ram
it runs on native fedora no vm

On Sun, Nov 29, 2009 at 4:22 AM, Mark Robson  wrote:

> 2009/11/28 
>
>> thanks i dont have more than 1 node ie just one node operation
>> so dunno if the timeout increase will help
>>
>
> Presumably this is a test system on a vmware; it may have insufficient
> memory.
>
> I'd say make sure that your test virtual machine (vmware etc) has at least
> 1.5G of ram allocated and the Java VM is tuned suitably. Don't run on a
> 32-bit system as this limits the size of the Java heap too small.
>
> I'm speculating here, but you didn't give us much to work on.
>
> A production Cassandra node should have at least 16G of ram as it's really
> cheap. Ram doesn't use much power and power is the main consideration for
> datacentres nowadays. A 64-bit system is necessary as otherwise you'll be
> limited to a <3G Java heap, which makes having 16G ram pointless.
>
> Mark
>



-- 
Bidegg worlds best auction site
http://bidegg.com


Re: java.util.concurrent.TimeoutException: Operation timed out - received only 0 responses from .

2009-11-29 Thread Mark Robson
2009/11/28 

> thanks i dont have more than 1 node ie just one node operation
> so dunno if the timeout increase will help
>

Presumably this is a test system on a vmware; it may have insufficient
memory.

I'd say make sure that your test virtual machine (vmware etc) has at least
1.5G of ram allocated and the Java VM is tuned suitably. Don't run on a
32-bit system as this limits the size of the Java heap too small.

I'm speculating here, but you didn't give us much to work on.

A production Cassandra node should have at least 16G of ram as it's really
cheap. Ram doesn't use much power and power is the main consideration for
datacentres nowadays. A 64-bit system is necessary as otherwise you'll be
limited to a <3G Java heap, which makes having 16G ram pointless.

Mark


Re: java.util.concurrent.TimeoutException: Operation timed out - received only 0 responses from .

2009-11-28 Thread mobiledreamers
thanks i dont have more than 1 node ie just one node operation
so dunno if the timeout increase will help

but trying it out

On Wed, Nov 25, 2009 at 11:16 AM, Freeman, Tim  wrote:

>  I use
>
>
>
>  3
>
>
>
> in storage-conf.xml, and for the most part that makes the timeouts go
> away.  My application would rather wait 30 seconds if needed, since it would
> otherwise retry.  YMMV.  I hear that Cassandra 0.5 will be better at
> avoiding the timeouts.
>
>
>
> Tim Freeman
> Email: tim.free...@hp.com
> Desk in Palo Alto: (650) 857-2581
> Home: (408) 774-1298
> Cell: (408) 348-7536 (No reception business hours Monday, Tuesday, and
> Thursday; call my desk instead.)
>
>
>
> *From:* mobiledream...@gmail.com [mailto:mobiledream...@gmail.com]
> *Sent:* Monday, November 23, 2009 12:26 PM
> *To:* cassandra-user@incubator.apache.org
> *Subject:* Re: java.util.concurrent.TimeoutException: Operation timed out
> - received only 0 responses from .
>
>
>
> this error keeps coming up...
>
> any ideas on how to avoid this error?
>
>
>
> On Wed, Nov 18, 2009 at 11:25 PM,  wrote:
>
> Can you plase tell what this error is ?
>
>
>
> ERROR - error writing key ruske
>
> *java.util.concurrent.TimeoutException: Operation timed out - received
> only 0 responses from  .*
>
> at
> org.apache.cassandra.service.QuorumResponseHandler.get(QuorumResponseHandler.java:88)
>
> at
> org.apache.cassandra.service.StorageProxy.insertBlocking(StorageProxy.java:164)
>
> at
> org.apache.cassandra.service.CassandraServer.doInsert(CassandraServer.java:468)
>
> at
> org.apache.cassandra.service.CassandraServer.batch_insert(CassandraServer.java:448)
>
> at
> org.apache.cassandra.service.Cassandra$Processor$batch_insert.process(Cassandra.java:854)
>
> at
> org.apache.cassandra.service.Cassandra$Processor.process(Cassandra.java:627)
>
> at
> org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:253)
>
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>
> at java.lang.Thread.run(Thread.java:619)
>
>
>
>
>
> Errors
>
>
>
>
> --
> Bidegg worlds best auction site
> http://bidegg.com
>



-- 
Bidegg worlds best auction site
http://bidegg.com


RE: java.util.concurrent.TimeoutException: Operation timed out - received only 0 responses from .

2009-11-25 Thread Freeman, Tim
I use

 3

in storage-conf.xml, and for the most part that makes the timeouts go away.  My 
application would rather wait 30 seconds if needed, since it would otherwise 
retry.  YMMV.  I hear that Cassandra 0.5 will be better at avoiding the 
timeouts.

Tim Freeman
Email: tim.free...@hp.com<mailto:tim.free...@hp.com>
Desk in Palo Alto: (650) 857-2581
Home: (408) 774-1298
Cell: (408) 348-7536 (No reception business hours Monday, Tuesday, and 
Thursday; call my desk instead.)

From: mobiledream...@gmail.com [mailto:mobiledream...@gmail.com]
Sent: Monday, November 23, 2009 12:26 PM
To: cassandra-user@incubator.apache.org
Subject: Re: java.util.concurrent.TimeoutException: Operation timed out - 
received only 0 responses from .

this error keeps coming up...
any ideas on how to avoid this error?

On Wed, Nov 18, 2009 at 11:25 PM, 
mailto:mobiledream...@gmail.com>> wrote:
Can you plase tell what this error is ?

ERROR - error writing key ruske
java.util.concurrent.TimeoutException: Operation timed out - received only 0 
responses from  .
at 
org.apache.cassandra.service.QuorumResponseHandler.get(QuorumResponseHandler.java:88)
at 
org.apache.cassandra.service.StorageProxy.insertBlocking(StorageProxy.java:164)
at 
org.apache.cassandra.service.CassandraServer.doInsert(CassandraServer.java:468)
at 
org.apache.cassandra.service.CassandraServer.batch_insert(CassandraServer.java:448)
at 
org.apache.cassandra.service.Cassandra$Processor$batch_insert.process(Cassandra.java:854)
at 
org.apache.cassandra.service.Cassandra$Processor.process(Cassandra.java:627)
at 
org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:253)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)


Errors



--
Bidegg worlds best auction site
http://bidegg.com


Re: java.util.concurrent.TimeoutException: Operation timed out - received only 0 responses from .

2009-11-23 Thread mobiledreamers
this error keeps coming up...
any ideas on how to avoid this error?

On Wed, Nov 18, 2009 at 11:25 PM,  wrote:

> Can you plase tell what this error is ?
>
> ERROR - error writing key ruske
> *java.util.concurrent.TimeoutException: Operation timed out - received
> only 0 responses from  .*
> at
> org.apache.cassandra.service.QuorumResponseHandler.get(QuorumResponseHandler.java:88)
> at
> org.apache.cassandra.service.StorageProxy.insertBlocking(StorageProxy.java:164)
> at
> org.apache.cassandra.service.CassandraServer.doInsert(CassandraServer.java:468)
> at
> org.apache.cassandra.service.CassandraServer.batch_insert(CassandraServer.java:448)
> at
> org.apache.cassandra.service.Cassandra$Processor$batch_insert.process(Cassandra.java:854)
> at
> org.apache.cassandra.service.Cassandra$Processor.process(Cassandra.java:627)
> at
> org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:253)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:619)
>
>
> Errors
>



-- 
Bidegg worlds best auction site
http://bidegg.com


Re: java.util.concurrent.TimeoutException: Operation timed out - received only 0 responses from .

2009-11-19 Thread Tim Underwood
I'm using Scala with my own Cassandra client and the splitting code was
hacked in to get around the exception.  So I'm not sure if my code will help
or not but it's basically:

===
var row = TheColumnFamily(key)
var count = 0

// dataToInsert is a map of column names to values
dataToInsert.foreach { case (name,value) =>
row(name) = value
count += 1

// Flush every 10,000 columns
if(count % 1 == 0) {
row.save
row = TheColumnFamily(key)
}
}

// Flush anything that's left over
row.save
===

When I get around to it I'll push the logic down to either my Row class and
have it auto-flush when it hits a column limit or modify my batchInsert
method to split the data into multiple batch_insert calls.

-Tim

On Thu, Nov 19, 2009 at 8:39 AM,  wrote:

> can you share code on how to split columns in cassdict or batch_insert?
> thanks
>
>
> On Thu, Nov 19, 2009 at 8:15 AM, Tim Underwood wrote:
>
>> I've seen also.  Sometimes it seems random and retrying the call works (I
>> think it might have happened during a compaction).  If I try doing a
>> batch_insert on a key with more than 200,000 columns (or so) I always get
>> this exception and have to break the inserts into smaller chunks.
>>
>> -Tim
>>
>>
>> On Wed, Nov 18, 2009 at 11:25 PM,  wrote:
>>
>>> Can you plase tell what this error is ?
>>>
>>> ERROR - error writing key ruske
>>> *java.util.concurrent.TimeoutException: Operation timed out - received
>>> only 0 responses from  .*
>>>  at
>>> org.apache.cassandra.service.QuorumResponseHandler.get(QuorumResponseHandler.java:88)
>>> at
>>> org.apache.cassandra.service.StorageProxy.insertBlocking(StorageProxy.java:164)
>>> at
>>> org.apache.cassandra.service.CassandraServer.doInsert(CassandraServer.java:468)
>>> at
>>> org.apache.cassandra.service.CassandraServer.batch_insert(CassandraServer.java:448)
>>> at
>>> org.apache.cassandra.service.Cassandra$Processor$batch_insert.process(Cassandra.java:854)
>>> at
>>> org.apache.cassandra.service.Cassandra$Processor.process(Cassandra.java:627)
>>> at
>>> org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:253)
>>> at
>>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>>> at
>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>>> at java.lang.Thread.run(Thread.java:619)
>>>
>>>
>>> Errors
>>>
>>
>>
>
>
> --
> Bidegg worlds best auction site
> http://bidegg.com
>


Re: java.util.concurrent.TimeoutException: Operation timed out - received only 0 responses from .

2009-11-19 Thread mobiledreamers
can you share code on how to split columns in cassdict or batch_insert?
thanks

On Thu, Nov 19, 2009 at 8:15 AM, Tim Underwood wrote:

> I've seen also.  Sometimes it seems random and retrying the call works (I
> think it might have happened during a compaction).  If I try doing a
> batch_insert on a key with more than 200,000 columns (or so) I always get
> this exception and have to break the inserts into smaller chunks.
>
> -Tim
>
>
> On Wed, Nov 18, 2009 at 11:25 PM,  wrote:
>
>> Can you plase tell what this error is ?
>>
>> ERROR - error writing key ruske
>> *java.util.concurrent.TimeoutException: Operation timed out - received
>> only 0 responses from  .*
>> at
>> org.apache.cassandra.service.QuorumResponseHandler.get(QuorumResponseHandler.java:88)
>> at
>> org.apache.cassandra.service.StorageProxy.insertBlocking(StorageProxy.java:164)
>> at
>> org.apache.cassandra.service.CassandraServer.doInsert(CassandraServer.java:468)
>> at
>> org.apache.cassandra.service.CassandraServer.batch_insert(CassandraServer.java:448)
>> at
>> org.apache.cassandra.service.Cassandra$Processor$batch_insert.process(Cassandra.java:854)
>> at
>> org.apache.cassandra.service.Cassandra$Processor.process(Cassandra.java:627)
>> at
>> org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:253)
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>> at java.lang.Thread.run(Thread.java:619)
>>
>>
>> Errors
>>
>
>


-- 
Bidegg worlds best auction site
http://bidegg.com


Re: java.util.concurrent.TimeoutException: Operation timed out - received only 0 responses from .

2009-11-19 Thread Tim Underwood
I've seen also.  Sometimes it seems random and retrying the call works (I
think it might have happened during a compaction).  If I try doing a
batch_insert on a key with more than 200,000 columns (or so) I always get
this exception and have to break the inserts into smaller chunks.

-Tim

On Wed, Nov 18, 2009 at 11:25 PM,  wrote:

> Can you plase tell what this error is ?
>
> ERROR - error writing key ruske
> *java.util.concurrent.TimeoutException: Operation timed out - received
> only 0 responses from  .*
> at
> org.apache.cassandra.service.QuorumResponseHandler.get(QuorumResponseHandler.java:88)
> at
> org.apache.cassandra.service.StorageProxy.insertBlocking(StorageProxy.java:164)
> at
> org.apache.cassandra.service.CassandraServer.doInsert(CassandraServer.java:468)
> at
> org.apache.cassandra.service.CassandraServer.batch_insert(CassandraServer.java:448)
> at
> org.apache.cassandra.service.Cassandra$Processor$batch_insert.process(Cassandra.java:854)
> at
> org.apache.cassandra.service.Cassandra$Processor.process(Cassandra.java:627)
> at
> org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:253)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:619)
>
>
> Errors
>