[ https://issues.apache.org/jira/browse/CASSANDRA-981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis reopened CASSANDRA-981: -------------------------------------- Getting this test failure in 0.6: [junit] Testcase: testSnitch(org.apache.cassandra.locator.DynamicEndpointSnitchTest): FAILED [junit] null [junit] junit.framework.AssertionFailedError [junit] at org.apache.cassandra.locator.DynamicEndpointSnitchTest.testSnitch(DynamicEndpointSnitchTest.java:70) > 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 > Assignee: Brandon Williams > Fix For: 0.6.5 > > Attachments: 981-0.6.txt, 981.txt > > > 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. - You can reply to this email to add a comment to the issue online.