cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sam Tunnicliffe (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-7947) Change error message when RR times out
Date Wed, 10 Dec 2014 10:20:12 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-7947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Sam Tunnicliffe updated CASSANDRA-7947:
---------------------------------------
    Attachment: 7947.txt

Attaching a simple patch which correctly sets the CL on the thrown exception. Looks like this
is only an issue when read requests following a digest mismatch time out, if we timeout waiting
on acks for the subsequent mutations, the correct CL is communicated.

> Change error message when RR times out
> --------------------------------------
>
>                 Key: CASSANDRA-7947
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7947
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Brandon Williams
>            Assignee: Sam Tunnicliffe
>            Priority: Minor
>             Fix For: 2.0.12
>
>         Attachments: 7947.txt
>
>
> When a quorum request detects a checksum mismatch, it then reads the data to repair the
mismatch by issuing a request at CL.ALL to the same endpoints  (SP.fetchRows)  If this request
in turn times out, this delivers a TOE to the client with a misleading message that mentions
CL.ALL, possibly causing them to think the request has gone cross-DC when it has not, it was
just slow due to timing out.



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

Mime
View raw message