Thank you for your advice.
Kazuo
(11/04/07 21:15), Kazuo YAGI wrote:
Thank both of you. I'll look it up from another view including
non-cassandra processes on the servers. Just guessing Nagios or
iptables or others causes it.
Kazuo
(11/04/05 22:55), Sasha Dolgy wrote:
I've been seeing
(the one that defaults to 7000) and disconnecting.
On Mon, Apr 4, 2011 at 4:14 AM, Kazuo YAGI wrote:
Solution: upgrade to 0.7.4, run scrub
Although I upgraded all my cassandra nodes from 0.7.0 to 0.7.4 and
ran nodetool scrub to all keyspaces, this EOFException error messages
didn't go away. Do you
know whether or not
these error messages are ignorable, because our application has been
working well before and after upgrading.
Thanks,
Kazuo
(11/03/28 11:19), Kazuo YAGI wrote:
I really thank you for your information.
I'll try to upgrade 0.7.4 and run scrub.
(11/03/25 22:39), Jonathan E
u don't have to
worry about this.) Note that nodetool scrub will snapshot your
data files before rebuilding, just in case.
Solution: upgrade to 0.7.4, run scrub
2011/3/25 Kazuo YAGI:
Hi everyone,
I'm running 10 cassandra nodes in total and updated 5 nodes
from 0.7.0 to 0.
va:73)
Caused by: java.io.EOFException
at java.io.DataInputStream.readInt(DataInputStream.java:375)
at
org.apache.cassandra.net.IncomingTcpConnection.run(IncomingTcpConnection.java:61)
--
Best,
Kazuo YAGI
