You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Gautam Kumar (JIRA)" <ji...@apache.org> on 2015/08/15 15:07:45 UTC
[jira] [Commented] (CASSANDRA-10020) Support eager retries for
range queries
[ https://issues.apache.org/jira/browse/CASSANDRA-10020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14698256#comment-14698256 ]
Gautam Kumar commented on CASSANDRA-10020:
------------------------------------------
It takes a long time for the liveEndpoints structure to get updated, the range query timing out gives a lot of problem. Any special reason why you don't issue the range queries on all the nodes.
> Support eager retries for range queries
> ---------------------------------------
>
> Key: CASSANDRA-10020
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10020
> Project: Cassandra
> Issue Type: New Feature
> Components: Core
> Reporter: Gautam Kumar
> Priority: Minor
>
> A simple query like `select * from table` may time out if one of the nodes fail.
> We had a 4-node cassandra cluster with RF=3 and CL=LOCAL_QUORUM.
> The range query is issued to only two as per ConsistencyLevel.java: liveEndpoints.subList(0, Math.min(liveEndpoints.size(), blockFor(keyspace)));
> If a node fails amongst this sublist, the query will time out. Why don't you issue range queries to all replicas?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)