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 this EOF in my system.log file occasionally as well.
Doesn't seem to be causing harm:
ERROR [Thread-22] 2011-04-05 20:37:22,562 AbstractCassandraDaemon.java
(line 112) Fatal exception in thread Thread[Thread-22,5,main]
java.io.IOError: java.io.EOFException
at
org.apache.cassandra.net.IncomingTcpConnection.run(IncomingTcpConnection.java:73)
Caused by: java.io.EOFException
at java.io.DataInputStream.readInt(DataInputStream.java:375)
at
org.apache.cassandra.net.IncomingTcpConnection.run(IncomingTcpConnection.java:61)
Firewall rules prevent anything but cassandra instances accessing
cassandra instances on port 7000 ...
This is with 0.7.4
-sd
On Tue, Apr 5, 2011 at 3:47 PM, Jonathan Ellis<jbel...@gmail.com> wrote:
Oops, I saw "EOFException" and jumped to "scrub."
But your EOF is coming from TCP. Something (almost certainly a
non-cassandra process) is connecting to the internal Cassandra
communication port (the one that defaults to 7000) and disconnecting.
On Mon, Apr 4, 2011 at 4:14 AM, Kazuo YAGI<ky...@zynga.co.jp> 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 have any ideas how to deal with it next?
Besides, it would be really useful if I could know whether or not
these error messages are ignorable, because our application has been
working well before and after upgrading.
Thanks,
Kazuo
