fatar exception after decommission
----------------------------------
Key: CASSANDRA-3233
URL: https://issues.apache.org/jira/browse/CASSANDRA-3233
Project: Cassandra
Issue Type: Bug
Components: Core
Affects Versions: 0.8.5
Environment: linux 2.6.32 (openvz, debian)
java sun 1.6.0_26:
sun-java6-bin 6.26-0squeeze1
sun-java6-jre 6.26-0squeeze1
Reporter: Zenek Kraweznik
after decommission node (succesful) i found in logfile information about fatal
exception:
INFO 20:19:16,753 Streaming to /10.117.199.233
INFO 21:11:11,699 Removing token 127605887595351923798765477786913079296 for
/10.117.199.234
INFO 21:11:11,699 Deleting any stored hints for 10.117.199.234
INFO 21:11:11,701 Announcing that I have left the ring for 30000ms
INFO 21:11:11,702 Enqueuing flush of Memtable-HintsColumnFamily@1635064453(0/0
serialized/live bytes, 1 ops)
INFO 21:11:11,703 Writing Memtable-HintsColumnFamily@1635064453(0/0
serialized/live bytes, 1 ops)
INFO 21:11:11,729 Completed flushing
/var/lib/cassandra/data/system/HintsColumnFamily-g-1-Data.db (64 bytes)
INFO 21:11:41,702 Shutting down MessageService...
INFO 21:11:41,704 Shutdown complete (no further commands will be processed)
INFO 21:11:41,704 MessagingService shutting down server thread.
INFO 21:11:41,706 Decommissioned
ERROR 21:11:44,261 Fatal exception in thread Thread[Thread-9632,5,main]
java.util.concurrent.RejectedExecutionException: ThreadPoolExecutor has shut
down
at
org.apache.cassandra.concurrent.DebuggableThreadPoolExecutor$1.rejectedExecution(DebuggableThreadPoolExecutor.java:60)
at
java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:767)
at
java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:658)
at
org.apache.cassandra.net.MessagingService.receive(MessagingService.java:490)
at
org.apache.cassandra.net.IncomingTcpConnection.run(IncomingTcpConnection.java:133)
INFO 21:43:22,198 Cassandra shutting down...
INFO 21:43:22,199 Stop listening to thrift clients
2 last lines are about stopping cassandra via init.d script.
Is that exception normal? If it is, then it should be not exception but normal
operation.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
