[
https://issues.apache.org/jira/browse/CASSANDRA-1314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12898710#action_12898710
]
Jonathan Ellis commented on CASSANDRA-1314:
-------------------------------------------
at least one person on IRC would like the order of nodes from Strategy (which i
believe is exposed almost directly by describe_ring) to be in algorithmic order
so he can easily pick non-overlapping ranges to process on each node locally.
so maybe moving Strategy back to a List (instead of the current Set) and making
that explicit guarantee is the easiest solution to both.
> snitch that prefers a single replica for all reads to a given key
> -----------------------------------------------------------------
>
> Key: CASSANDRA-1314
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1314
> Project: Cassandra
> Issue Type: New Feature
> Components: Core
> Reporter: Jonathan Ellis
> Assignee: Jonathan Ellis
> Priority: Minor
> Fix For: 0.7.0
>
> Attachments: SimpleSnitch.java, StaticPreferenceSnitch.java
>
>
> motivation is, if you reduce or eliminate read repair (CASSANDRA-930) then
> you can cache about RF times as much data in memory, than if you're
> scattering reads across all the replicas equally.
> making this data-center aware would be a nice improvement, but i'm just
> targetting a single DC here.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
