Return-Path: X-Original-To: apmail-ignite-issues-archive@minotaur.apache.org Delivered-To: apmail-ignite-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2200E19A08 for ; Mon, 21 Mar 2016 15:27:26 +0000 (UTC) Received: (qmail 13666 invoked by uid 500); 21 Mar 2016 15:27:26 -0000 Delivered-To: apmail-ignite-issues-archive@ignite.apache.org Received: (qmail 13625 invoked by uid 500); 21 Mar 2016 15:27:25 -0000 Mailing-List: contact issues-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ignite.apache.org Delivered-To: mailing list issues@ignite.apache.org Received: (qmail 13606 invoked by uid 99); 21 Mar 2016 15:27:25 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 21 Mar 2016 15:27:25 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 772372C14F6 for ; Mon, 21 Mar 2016 15:27:25 +0000 (UTC) Date: Mon, 21 Mar 2016 15:27:25 +0000 (UTC) From: "Anton Vinogradov (JIRA)" To: issues@ignite.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (IGNITE-708) Need to remove background partition exchange 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/IGNITE-708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-708: ------------------------------------ Assignee: (was: Gianfranco Murador) > Need to remove background partition exchange > -------------------------------------------- > > Key: IGNITE-708 > URL: https://issues.apache.org/jira/browse/IGNITE-708 > Project: Ignite > Issue Type: Task > Affects Versions: ignite-1.4 > Reporter: Yakov Zhdanov > Priority: Blocker > Labels: datagrid > Fix For: 1.6 > > > Now every node sends its partition map to cache coordinator (which is the oldest node in topology) and coordinator spreads full partition map to every node in topology. This happens for each cache separately. This seems to take place even if there were no changes to local partition maps. Given we guarantee communication message delivery this background process seems to be an overkill. > Exchange should happen only if any changes took place. > After dynamic cache start has been introduced, we can have significant amount of live caches at some point of app lifecycle and app may suffer from background exchange which is obviously not a requirement (and may be never has been the one). -- This message was sent by Atlassian JIRA (v6.3.4#6332)