ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yakov Zhdanov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-708) Need to remove background partition exchange
Date Tue, 06 Oct 2015 12:53:26 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14944979#comment-14944979
] 

Yakov Zhdanov commented on IGNITE-708:
--------------------------------------

Gian,

you removed body of {{onTimeout}} method, but {{ResendTimeoutObject}} still gets scheduled.
This is not correct. Please also note that partitions resending is scheduled from different
places and can't be just removed. Many tests failed. See TeamCity results for your PR: http://204.14.53.153/project.html?projectId=Ignite&tab=projectOverview&branch_Ignite=pull%2F129%2Fhead
(please make sure you have TC green before submitting anything to review)

You should continue your investigation. Identify place in code when each node sends its partitions
to oldest node and change it so partitions get sent only if anything changed locally.

Thanks!


> 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: ignite-1.5, ignite-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