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 7F07F10BDC for ; Tue, 18 Jun 2013 17:28:21 +0000 (UTC) Received: (qmail 84735 invoked by uid 500); 18 Jun 2013 17:28:21 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 84722 invoked by uid 500); 18 Jun 2013 17:28:21 -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 84698 invoked by uid 99); 18 Jun 2013 17:28:20 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Jun 2013 17:28:20 +0000 Date: Tue, 18 Jun 2013 17:28:20 +0000 (UTC) From: "Jonathan Ellis (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (CASSANDRA-5632) Cross-DC bandwidth-saving broken 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-5632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis updated CASSANDRA-5632: -------------------------------------- Attachment: 5632-v2.txt v2 attached that rebases and does some further cleanup to improve trace messages. > Cross-DC bandwidth-saving broken > -------------------------------- > > Key: CASSANDRA-5632 > URL: https://issues.apache.org/jira/browse/CASSANDRA-5632 > Project: Cassandra > Issue Type: Bug > Components: Core > Affects Versions: 1.2.0 > Reporter: Jonathan Ellis > Assignee: Jonathan Ellis > Fix For: 1.2.6 > > Attachments: 5632.txt, 5632-v2.txt, cassandra-topology.properties, fix_patch_bug.log > > > We group messages by destination as follows to avoid sending multiple messages to a remote datacenter: > {code} > // Multimap that holds onto all the messages and addresses meant for a specific datacenter > Map> dcMessages > {code} > When we cleaned out the MessageProducer stuff for 2.0, this code > {code} > Multimap messages = dcMessages.get(dc); > ... > messages.put(producer.getMessage(Gossiper.instance.getVersion(destination)), destination); > {code} > turned into > {code} > Multimap messages = dcMessages.get(dc); > ... > messages.put(rm.createMessage(), destination); > {code} > Thus, we weren't actually grouping anything anymore -- each destination replica was stored under a separate Message key, unlike under the old CachingMessageProducer. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira