cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vijay (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-3687) Local range scans are not run on the read stage
Date Fri, 18 May 2012 00:55:02 GMT


Vijay commented on CASSANDRA-3687:

+10, one thing which i noticed was will it be better to remove (coz the localnode might not
be in position 0).

if (handler.endpoints.size() == 1 && handler.endpoints.get(0).equals(FBUtilities.getBroadcastAddress())

and add it to 

for (InetAddress endpoint : handler.endpoints)
    if (endpoint.equals(FBUtilities.getBroadcastAddress())
        logger.debug("reading data locally");
        StageManager.getStage(Stage.READ).execute(new LocalRangeSliceRunnable(nodeCmd, handler));

similar to fetchRows?
> Local range scans are not run on the read stage
> -----------------------------------------------
>                 Key: CASSANDRA-3687
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Jonathan Ellis
>            Assignee: Jonathan Ellis
>            Priority: Minor
>             Fix For: 1.2
> Running directly on the client request/StorageProxy thread means we're now allowing one
range scan per thrift thread instead of one per read stage thread [which may be more, or less,
depending on thrift server mode], and it bypasses the "drop hopeless requests" overcapacity
protection built in there. 

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message