[
https://issues.apache.org/jira/browse/IGNITE-708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15182232#comment-15182232
]
Gianfranco Murador commented on IGNITE-708:
-------------------------------------------
I think it is too delicate to touch this mechanism without providing a huge
amount of non-regression tests. I do not think I can accomplish this task in
the limited time that I can devote to Ignite. Sorry for that :(. The ticket can
be reassigned if necessary.
> 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.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)
