[
https://issues.apache.org/jira/browse/CASSANDRA-14311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16397960#comment-16397960
]
Jeff Jirsa edited comment on CASSANDRA-14311 at 3/14/18 1:44 AM:
-----------------------------------------------------------------
Interesting. If the page border spans to another token, you'd still want to
fill the whole page, wouldn't you? I assume so.
Doesn't the driver already have an option to choose the next host in the ring
if it determines the paging state is beyond the original coordinator's boundary?
was (Author: jjirsa):
Interesting. If the page border spans to another token, you'd still want to
fill the whole page, wouldn't you? I assume sos.
Doesn't the driver already have an option to choose the next host in the ring
if it determines the paging state is beyond the original coordinator's boundary?
> Allow Token-Aware drivers for range scans
> -----------------------------------------
>
> Key: CASSANDRA-14311
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14311
> Project: Cassandra
> Issue Type: Improvement
> Components: Coordination
> Reporter: Avi Kivity
> Priority: Major
>
> Currently, range scans are not token aware. This means that an extra hop is
> needed for most requests. Since range scans are usually data intensive, this
> causes significant extra traffic.
>
> Token awareness could be enabled by having the coordinator return the token
> for the next (still unread) row in the response, so the driver can select a
> next coordinator that owns this row.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
