ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anton Vinogradov (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (IGNITE-708) Need to remove background partition exchange
Date Tue, 29 Mar 2016 12:10:25 GMT

     [ https://issues.apache.org/jira/browse/IGNITE-708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Anton Vinogradov resolved IGNITE-708.
-------------------------------------
    Resolution: Duplicate

> 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: Anton Vinogradov
>            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)

Mime
View raw message