cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-9460) NullPointerException Creating Digest
Date Mon, 25 May 2015 14:16:17 GMT


Jonathan Ellis commented on CASSANDRA-9460:

Short reads are when a query comes in with LIMIT N, and each replica returns N rows to the
coordinator, but after merging the results together the coordinator has less than N rows left
because of non-shared tombstones.  At that point the coordinator needs to request extra rows
from the replicas to satisfy the original query.

Look for {{short reads}} in StorageProxy.

> NullPointerException Creating Digest
> ------------------------------------
>                 Key: CASSANDRA-9460
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Tyler Hobbs
>            Assignee: Stefania
>             Fix For: 2.1.x
>         Attachments: node2.log
> In the {{consistency_test.TestConsistency.short_read_test}} dtest against cassandra-2.1,
the following error occured:
> {noformat}
> ERROR [ReadRepairStage:3] 2015-05-22 16:35:25,034 - Exception
in thread Thread[ReadRepairStage:3,5,main]
> java.lang.NullPointerException: null
>     at org.apache.cassandra.db.ColumnFamily.updateDigest( ~[main/:na]
>     at org.apache.cassandra.db.ColumnFamily.digest( ~[main/:na]
>     at org.apache.cassandra.service.RowDigestResolver.resolve(
>     at org.apache.cassandra.service.RowDigestResolver.resolve(
>     at org.apache.cassandra.service.ReadCallback$
>     at java.util.concurrent.ThreadPoolExecutor.runWorker(
>     at java.util.concurrent.ThreadPoolExecutor$
>     at ~[na:1.7.0_80]
> {noformat}
> From a glance at the code in the stacktrace, it looks like there was a null cell in the
ColumnFamily that we were creating a digest of.  This error is probably particular to "short
> Here's the failing test:
 I've attached the logs for the node with the error.
> We saw this issue against 2.1, but the problem may also exist with 2.0 and/or 2.2.

This message was sent by Atlassian JIRA

View raw message