cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Markus (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-9562) Queries are not possible anymore after some time
Date Wed, 10 Jun 2015 08:30:00 GMT


Markus commented on CASSANDRA-9562:

I've upgraded to 2.1.6 today, let's see if the issue appears again with that version.

> Queries are not possible anymore after some time
> ------------------------------------------------
>                 Key: CASSANDRA-9562
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Markus
> We run cassandra 2.1.5 installation with 3 nodes on different debian wheezy VMs. Now
we have the issue that after some days of operation without problems, suddenly selects and
inserts to a table are no longer possible. In the logs we see the following error message:
> {code}com.datastax.driver.core.exceptions.ReadTimeoutException: Cassandra timeout during
read query at consistency QUORUM (2 responses were required but only 1 replica responded)
> at com.datastax.driver.core.exceptions.ReadTimeoutException.copy(
> When I execute nodetool status on each node, it shows me that all nodes are in Status=Up
and State=Normal.{code}
> If I run nodetool repair on a node I see thousands of exceptions like:
> 2015-06-03 16:40:58,023 ERROR [AntiEntropySessions:17] - [repair
#858c8470-09fe-11e5-930b-d16ee278cb3a] session completed with the following error
> {code} Failed during snapshot creation.
>     at
>     at$2.onFailure( ~[apache-cassandra-2.1.5.jar:2.1.5]
>     at$ ~[guava-16.0.jar:na]
>     at java.util.concurrent.ThreadPoolExecutor.runWorker(
>     at java.util.concurrent.ThreadPoolExecutor$
>     at [na:1.8.0_45]{code}
> in the log. To repair cassandra, I need to restart the cassandra daemon on every node
and then run nodetool repair on every node (Which after the restart of the nodes works without
throwing the exception). Then it works again for 2-3 days until the same issue appears again.

This message was sent by Atlassian JIRA

View raw message