Return-Path: X-Original-To: apmail-cassandra-commits-archive@www.apache.org Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id F21DA19EB2 for ; Wed, 6 Apr 2016 17:00:30 +0000 (UTC) Received: (qmail 84257 invoked by uid 500); 6 Apr 2016 17:00:30 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 84198 invoked by uid 500); 6 Apr 2016 17:00:30 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 84175 invoked by uid 99); 6 Apr 2016 17:00:30 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Apr 2016 17:00:30 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 76B112C1F8E for ; Wed, 6 Apr 2016 17:00:30 +0000 (UTC) Date: Wed, 6 Apr 2016 17:00:30 +0000 (UTC) From: "Jeremy Hanna (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CASSANDRA-11488) Bug or not?: coordinator using SimpleSnitch may query other nodes for copies of local data MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CASSANDRA-11488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15228643#comment-15228643 ] Jeremy Hanna commented on CASSANDRA-11488: ------------------------------------------ Giving this some more though, I think we need to document the distinction. I didn't realize that the dynamic snitch would route away from local nodes when using TokenAware load balancing for example. It does make sense if that local node is really behind on LCS or has some heavier operation going on. I just don't think people expect TokenAware would get routed to another replica necessarily. In any case I agree that documentation is probably the best outcome for now unless there is data that shows that this is insufficient. > Bug or not?: coordinator using SimpleSnitch may query other nodes for copies of local data > ------------------------------------------------------------------------------------------- > > Key: CASSANDRA-11488 > URL: https://issues.apache.org/jira/browse/CASSANDRA-11488 > Project: Cassandra > Issue Type: Bug > Components: Coordination > Reporter: Jim Witschey > Assignee: Stefania > Priority: Minor > Labels: doc-impacting > > As [~Stefania] explains [in this JIRA comment|https://issues.apache.org/jira/browse/CASSANDRA-11225?focusedCommentId=15221059&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15221059], {{SimpleSnitch}} does not implement {{IEndpointSnitch.sortByProximity(localhost, liveendpoints)}}, so a query for data on the coordinator may query other nodes. That seems like unnecessary work to me, and on that note, Stefania woonders [in this JIRA comment|https://issues.apache.org/jira/browse/CASSANDRA-11225?focusedCommentId=15223598&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15223598] - should this be considered a bug? > Stefania, I'm assigning you here -- could you find the right people to involve in this discussion? -- This message was sent by Atlassian JIRA (v6.3.4#6332)