You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Anton Vinogradov (JIRA)" <ji...@apache.org> on 2015/11/30 09:16:10 UTC
[jira] [Comment Edited] (IGNITE-708) Need to remove background
partition exchange
[ https://issues.apache.org/jira/browse/IGNITE-708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15031458#comment-15031458 ]
Anton Vinogradov edited comment on IGNITE-708 at 11/30/15 8:15 AM:
-------------------------------------------------------------------
Gianfranco,
I'm not sure I understand you. Could you please rephrase question?
In case you asking me for changes list done according to 1093, you can see them at
commit 242d988a077878cca93f7bec85af3438a94e44d7
was (Author: avinogradov):
Gianfranco,
I'm not sure I understand you. Could you please rephrase question?
> 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
> Assignee: Gianfranco Murador
> Priority: Blocker
> Labels: datagrid
> Fix For: 1.5, 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)