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

Paulo Motta commented on CASSANDRA-10801:
-----------------------------------------

bq. I don't understand why the first query didn't send request to other nodes 
while the last one did.

Reads are only sent to the amount of nodes necessary to satisfy consistency, so 
if you read at {{ONE}} the query is only sent to 1 node. If read repair is 
triggered, the query is sent to more nodes.

Are you sure your writes were at {{ALL}} consistency? The first report by some 
other person says the write was at {{ONE}}. Because if you had dropped 
mutations then some of your {{ALL}} writes have failed, and those might be 
causing inconsistencies. 

Unfortunately it's not possible to identify what may be causing this with the 
info you provided so you should try to provide more specific reproduction 
steps. As a workaround, you may try to recreate the table with a different name 
and see if the problem persists.

> Unexplained inconsistent data with Cassandra 2.1
> ------------------------------------------------
>
>                 Key: CASSANDRA-10801
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10801
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Imri Zvik
>             Fix For: 2.1.x
>
>         Attachments: trace2.log, tracing.log
>
>
> We are experiencing weird behavior which we cannot explain.
> We have a CF, with RF=3, and we are writing and reading data to it with 
> consistency level of ONE.
> For some reason, we see inconsistent results when querying for data.
> Even for rows that were written a day ago, we're seeing inconsistent results 
> (1 replca has the data, the two others don't).
> Now, I would expect to see timeouts/dropped mutations, but all relevant 
> counters are not advancing, and I would also expect hints to fix this 
> inconsistency within minutes, but yet it doesn't.
> {code}
> cqlsh:testing> SELECT WRITETIME(last_update),site_id, tree_id, individual_id, 
> last_update FROM testcf WHERE site_id = 229673621 AND tree_id = 9 AND 
> individual_id = 9032483;            
>  writetime(last_update) | site_id   | tree_id | individual_id | last_update
> ------------------------+-----------+---------+---------------+-------------
>        1448988343028000 | 229673621 |       9 |       9032483 |  1380912397
> (1 rows)
> cqlsh:testing> SELECT WRITETIME(last_update),site_id, tree_id, individual_id, 
> last_update FROM testcf WHERE site_id = 229673621 AND tree_id = 9 AND 
> individual_id = 9032483;
> site_id   | tree_id | individual_id | last_update
> -----------+---------+---------------+-------------
> (0 rows)
> cqlsh:testing> SELECT dateof(now()) FROM system.local ;
>  dateof(now())
> --------------------------
>  2015-12-02 14:48:44+0000
> (1 rows)
> {code}
> We are running with Cassandra 2.1.11 with Oracle Java 1.8.0_65-b17



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to