[ 
https://issues.apache.org/jira/browse/CASSANDRA-14167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16383782#comment-16383782
 ] 

Jim Wartnick edited comment on CASSANDRA-14167 at 3/2/18 7:20 PM:
------------------------------------------------------------------

I am having the exact same problem. Upgraded to Cassandra 3.11.1. I have a 
reproducible case with a record.

I even tried copying the data out to a flat-file, truncating the table, and 
re-loading it back in. Then flushed the memtables and re-queried a single, 
random, record which fails with consistency LOCAL_QUORUM but works fine with 
consistency ONE OR works fine if you don't specify the column name (e.g. SELECT 
*). 

One workaround that worked for us - as this is NOT a production environment 
yet, was to set the RF=1 on the keyspaces that contained the "counter" tables. 
By doing that the CF of QUORUM equates to 1, which then fixes the issue (no 
read repairs or validations required). Obviously if this was production, I 
would have some concerns regarding data availability, but for now, this is a 
workaround that may work for someone else.

 


was (Author: jwartnic):
I am having the exact same problem. Upgraded to Cassandra 3.11.1. I have a 
reproducible case with a record.

I even tried copying the data out to a flat-file, truncating the table, and 
re-loading it back in. Then flushed the memtables and re-queried a single, 
random, record which fails with consistency LOCAL_QUORUM but works fine with 
consistency ONE OR works fine if you don't specify the column name (e.g. SELECT 
*). 

 

 

> IndexOutOfBoundsException when selecting column counter and consistency quorum
> ------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-14167
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-14167
>             Project: Cassandra
>          Issue Type: Bug
>         Environment: Cassandra 3.11.1
> Ubuntu 14-04
>            Reporter: Tristan Last
>            Priority: Major
>
> This morning I upgraded my cluster from 3.11.0 to 3.11.1 and it appears when 
> I perform a query on a counter specifying the column name cassandra throws 
> the following exception:
> {code:java}
> WARN [ReadStage-1] 2018-01-15 10:58:30,121 
> AbstractLocalAwareExecutorService.java:167 - Uncaught exception on thread 
> Thread[ReadStage-1,5,main]: {}
> java.lang.IndexOutOfBoundsException: null
> java.nio.Buffer.checkIndex(Buffer.java:546) ~[na:1.8.0_144]
> java.nio.HeapByteBuffer.getShort(HeapByteBuffer.java:314) ~[na:1.8.0_144]
> org.apache.cassandra.db.context.CounterContext.headerLength(CounterContext.java:173)
>  ~[apache-cassandra-3.11.1.jar:3.11.1]
> org.apache.cassandra.db.context.CounterContext.updateDigest(CounterContext.java:696)
>  ~[apache-cassandra-3.11.1.jar:3.11.1]
> org.apache.cassandra.db.rows.AbstractCell.digest(AbstractCell.java:126) 
> ~[apache-cassandra-3.11.1.jar:3.11.1]
> org.apache.cassandra.db.rows.AbstractRow.digest(AbstractRow.java:73) 
> ~[apache-cassandra-3.11.1.jar:3.11.1]
> org.apache.cassandra.db.rows.UnfilteredRowIterators.digest(UnfilteredRowIterators.java:181)
>  ~[apache-cassandra-3.11.1.jar:3.11.1]
> org.apache.cassandra.db.partitions.UnfilteredPartitionIterators.digest(UnfilteredPartitionIterators.java:263)
>  ~[apache-cassandra-3.11.1.jar:3.11.1]
> org.apache.cassandra.db.ReadResponse.makeDigest(ReadResponse.java:120) 
> ~[apache-cassandra-3.11.1.jar:3.11.1]
> org.apache.cassandra.db.ReadResponse.createDigestResponse(ReadResponse.java:87)
>  ~[apache-cassandra-3.11.1.jar:3.11.1]
> org.apache.cassandra.db.ReadCommand.createResponse(ReadCommand.java:345) 
> ~[apache-cassandra-3.11.1.jar:3.11.1]
> org.apache.cassandra.db.ReadCommandVerbHandler.doVerb(ReadCommandVerbHandler.java:50)
>  ~[apache-cassandra-3.11.1.jar:3.11.1]
> org.apache.cassandra.net.MessageDeliveryTask.run(MessageDeliveryTask.java:66) 
> ~[apache-cassandra-3.11.1.jar:3.11.1]
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
> ~[na:1.8.0_144]
> org.apache.cassandra.concurrent.AbstractLocalAwareExecutorService$FutureTask.run(AbstractLocalAwareExecutorService.java:162)
>  ~[apache-cassandra-3.11.1.jar:3.11.1]
> org.apache.cassandra.concurrent.AbstractLocalAwareExecutorService$LocalSessionFutureTask.run(AbstractLocalAwareExecutorService.java:134)
>  [apache-cassandra-3.11.1.jar:3.11.1]
> org.apache.cassandra.concurrent.SEPWorker.run(SEPWorker.java:109) 
> [apache-cassandra-3.11.1.jar:3.11.1]
> java.lang.Thread.run(Thread.java:748) [na:1.8.0_144]
> {code}
> Query works completely find on consistency level ONE but not on QUORUM. 
> Is this possibly related to CASSANDRA-11726?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to