Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Fri, 7 Aug 2015 20:55:45 +0000 (UTC)
From: "Gautam Kumar (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12853051.1438980937000.9270.1438980945651@Atlassian.JIRA>
In-Reply-To: <JIRA.12853051.1438980937000@Atlassian.JIRA>
References: <JIRA.12853051.1438980937000@Atlassian.JIRA>
 <JIRA.12853051.1438980937311@arcas>
Subject: [jira] [Created] (CASSANDRA-10020) Range queries don't go on all
 replicas.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Gautam Kumar created CASSANDRA-10020:
----------------------------------------

             Summary: Range queries don't go on all replicas. 
                 Key: CASSANDRA-10020
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10020
             Project: Cassandra
          Issue Type: Bug
          Components: Core
            Reporter: Gautam Kumar
            Priority: Critical


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)