That's it! Nagios causes this message. I should have noticed it
when I found the message appeared every exactly 5 minutes.
define command{
command_namecheck_cassandra_node
command_line$USER1$/check_tcp -H $HOSTADDRESS$ -p 7000 -t 5 -E -M crit
}
The issue is settled now. Thank you
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 causin
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.c
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 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 whethe
I really hank you for your information.
I'll try to upgrade 0.7.4 and run scrub.
(11/03/25 22:39), Jonathan Ellis wrote:
from NEWS.txt:
Upgrading
-
- 0.7.1 and 0.7.2 shipped with a bug that caused incorrect row-level
bloom filters to be generated when compacting sstables gen
from NEWS.txt:
Upgrading
-
- 0.7.1 and 0.7.2 shipped with a bug that caused incorrect row-level
bloom filters to be generated when compacting sstables generated
with earlier versions. This would manifest in IOExceptions during
column name-based queries. 0.7.3 provid
Hi everyone,
I'm running 10 cassandra nodes in total and updated 5 nodes
from 0.7.0 to 0.7.2 one by one like below.
# sudo /etc/init.d/cassandra stop
# sudo yum update cassandra-0.7.2-4
# sudo /etc/init.d/cassandra start
After updating, those 5 updated nodes keep outputting error messages to
/v
