[
https://issues.apache.org/jira/browse/CASSANDRA-981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12857969#action_12857969
]
Ryan King commented on CASSANDRA-981:
-------------------------------------
I'm sure you thought about this, but in cases where you're using the
RackAwareStrategy, the dynamic snitch will need to yield consistent results,
otherwise, you could create situations where the natural endpoints for a token
keep changing depending on network performance.
> Dynamic endpoint snitch
> -----------------------
>
> Key: CASSANDRA-981
> URL: https://issues.apache.org/jira/browse/CASSANDRA-981
> Project: Cassandra
> Issue Type: New Feature
> Components: Core
> Reporter: Jonathan Ellis
> Fix For: 0.7
>
>
> An endpoint snitch that automatically and dynamically infers "distance" to
> other machines without having to explicitly configure rack and datacenter
> positions solves two problems:
> The killer feature here is adapting to things like compaction or a
> failing-but-not-yet-dead disk. This is important, since when we are doing
> reads we pick the "closest" replica for actually reading data from (and only
> read md5s from other replicas). This means that if the closest replica by
> network topology is temporarily slow due to compaction (for instance), we'll
> have to block for its reply even if we get the other replies much much faster.
> Not having to manually re-sync your configuration with your network topology
> when changes (adding machines) are made is a nice bonus.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
