[
https://issues.apache.org/jira/browse/CASSANDRA-13363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16115515#comment-16115515
]
Jeff Jirsa commented on CASSANDRA-13363:
----------------------------------------
{quote}
And worth to mention that 3 nodes Cassandra cluster becomes completely
unreposnsive after that exception.
Exception itself occures on all 3 nodes.
{quote}
Does a cluster restart help, or does it stay broken?
Did you recently do any changes? Changing schemas? Do you see any signs of
physical hardware errors (interface counters showing errors)?
> java.lang.ArrayIndexOutOfBoundsException: null
> ----------------------------------------------
>
> Key: CASSANDRA-13363
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13363
> Project: Cassandra
> Issue Type: Bug
> Environment: CentOS 6, Cassandra 3.10
> Reporter: Artem Rokhin
> Priority: Critical
>
> Constantly see this error in the log without any additional information or a
> stack trace.
> {code}
> Exception in thread Thread[MessagingService-Incoming-/10.0.1.26,5,main]
> {code}
> {code}
> java.lang.ArrayIndexOutOfBoundsException: null
> {code}
> Logger: org.apache.cassandra.service.CassandraDaemon
> Thrdead: MessagingService-Incoming-/10.0.1.12
> Method: uncaughtException
> File: CassandraDaemon.java
> Line: 229
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
