You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "zhaoyan (JIRA)" <ji...@apache.org> on 2017/08/25 06:42:00 UTC

[jira] [Issue Comment Deleted] (CASSANDRA-13363) java.lang.ArrayIndexOutOfBoundsException: null

     [ https://issues.apache.org/jira/browse/CASSANDRA-13363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

zhaoyan updated CASSANDRA-13363:
--------------------------------
    Comment: was deleted

(was: use the Command.Index as the "USING INDEX"。 (for CASSANDRA-10214 ) and  make sure the field never changes and is only set once at construction time。 

without a protocol change.

I think it is a good idea. 

And add one another cache field  (that do not participate in serialization, only use as cache local) to save  the index cassandra lookup?  )

> 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
>            Assignee: Aleksey Yeschenko
>            Priority: Critical
>             Fix For: 3.0.x, 3.11.x, 4.x
>
>
> 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-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org