I found the solution to this problem. I was sending the same message to
all nodes, with the same ID, and that was apparently causing problems
somehow. It is solved anyway.
Alexander
> Thank you for your answer, however I am pretty sure that's not it. I have
> a small-two node cluster for developm
Thank you for your answer, however I am pretty sure that's not it. I have
a small-two node cluster for development testing, and I have loaded it
with data in a way that responses to my queries usually have about 5
short rows (which I think is not very much).
First of all, if I do it like this,
I would guess that sending a bunch of range requests simultaneously
overwhelms the targets (range scans are expensive), so you're timing
out simply because it couldn't finish all of them within rpc_timeout.
Solution: don't do that, or increase rpc_timeout.
On Wed, Jan 12, 2011 at 3:03 AM, wrote
