[
https://issues.apache.org/jira/browse/CASSANDRA-8479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14604787#comment-14604787
]
Anuj Wadehra commented on CASSANDRA-8479:
-----------------------------------------
@Sam I think it's an issue. As you mentioned in comment: "At least one of the
digests doesn't match, triggering a blocking full read against all the replicas
that were sent digest requests - which includes the down node in the remote DC."
Blocking full read must be triggered ONLY against the replicas that were sent
digest requests, Why did digest requests went to Remote DC when read CL was
LOCAL_QUORUM? This seems to be a major problem.
Should I reopen the JIRA ?
> Timeout Exception on Node Failure in Remote Data Center
> -------------------------------------------------------
>
> Key: CASSANDRA-8479
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8479
> Project: Cassandra
> Issue Type: Bug
> Components: API, Core, Tools
> Environment: Unix, Cassandra 2.0.11
> Reporter: Amit Singh Chowdhery
> Assignee: Sam Tunnicliffe
> Priority: Minor
> Attachments: TRACE_LOGS.zip
>
>
> Issue Faced :
> We have a Geo-red setup with 2 Data centers having 3 nodes each. When we
> bring down a single Cassandra node down in DC2 by kill -9 <Cassandra-pid>,
> reads fail on DC1 with TimedOutException for a brief amount of time (15-20
> sec~).
> Reference :
> Already a ticket has been opened/resolved and link is provided below :
> https://issues.apache.org/jira/browse/CASSANDRA-8352
> Activity Done as per Resolution Provided :
> Upgraded to Cassandra 2.0.11 .
> We have two 3 node clusters in two different DCs and if one or more of the
> nodes go down in one Data Center , ~5-10% traffic failure is observed on the
> other.
> CL: LOCAL_QUORUM
> RF=3
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
