OK, I wil try ot update the cassandra to 1.0.9 or 1.1.0 and update hector
to 1.0.x
Hope it could rescue me.
Thanks a lot~~
2012/4/24 Ji Cheng
> The tpstats shows there was no read request pending on this node. Maybe
> you should have a look at the other nodes first.
>
> But my suggestion is to
The tpstats shows there was no read request pending on this node. Maybe you
should have a look at the other nodes first.
But my suggestion is to upgrade hector to 1.0.x if possible. Hector 0.7 is
for cassandra 0.7. Just FYI, we had some issues when upgrading cassandra
from 0.8 to 1.0. And the prob
Thank you very much for your replay~
The full message like this:
DEBUG [Thread-6] 2012-04-24 21:04:11,024 IncomingTcpConnection.java (line
116) Version is now 3
During "blocking time" I only saw this message(*appendix shown) *and seems
everything is blocked.
I logged all cassandra calling time i
If you set trace level for IncomingTCPConnection, the message "Version
is now ..." will be printed for every inter-cassandra message received
by the node, including Gossip.
Enabling this log in high traffic will saturate IO for your log disk by itself.
You should better to inspect nodetool tpstats
Does any one have idea for this? Thanks~
2012/4/24 马超
> Hi all,
>
> I have some troubles of cassandra in my production:
>
> I build up a RPC server which using hector client to manipulate the
> cassandra. Wired things happen nowadays: the latency of RPC sometimes
> becames very high (10seconds~7
Hi all,
I have some troubles of cassandra in my production:
I build up a RPC server which using hector client to manipulate the
cassandra. Wired things happen nowadays: the latency of RPC sometimes
becames very high (10seconds~70seconds) in several minutes and reduce
to normal level (30ms in aver
