[
https://issues.apache.org/jira/browse/CASSANDRA-1314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis updated CASSANDRA-1314:
--------------------------------------
Attachment: SimpleSnitch.java
for 0.6 we'll have to "cheat" and rely on our knowledge that the ordering we
already have is in token order for the key in question.
The problem is that the snitch needs to return different nodes for different
keys given the same set of addresses, and it doesn't have enough information to
do that.
> 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.
