[
https://issues.apache.org/jira/browse/CASSANDRA-13363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16131564#comment-16131564
]
zhaoyan commented on CASSANDRA-13363:
-------------------------------------
Hi @Sam Tunnicliffe
Thank you for your patient explanation.
I has one more question：
"This would partially undo CASSANDRA-10215 and require each replica to figure
out which index to use, "
Does it take a lot of time to do "the lookup to determine which index to use "?
1=>send the command to other replica, must after the local replica figure out
which index to use .
2=>send to all replica, all replica figure it out itself.
which looks better?
> 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: zhaoyan
> 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: [email protected]
For additional commands, e-mail: [email protected]
