[
https://issues.apache.org/jira/browse/IGNITE-11011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16798804#comment-16798804
]
Ignite TC Bot commented on IGNITE-11011:
----------------------------------------
{panel:title=--> Run :: All: No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3361394&buildTypeId=IgniteTests24Java8_RunAll]
> Initialize components with grid disco data when NodeAddFinished message is
> received
> -----------------------------------------------------------------------------------
>
> Key: IGNITE-11011
> URL: https://issues.apache.org/jira/browse/IGNITE-11011
> Project: Ignite
> Issue Type: Improvement
> Reporter: Sergey Chugunov
> Assignee: Sergey Chugunov
> Priority: Major
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> There is an issue when CacheProcessor on fresh coordinator (the very first
> node in new topology) receives grid discovery data from another cluster that
> died before this node has joined its topology but after sending NodeAdded
> message.
> IGNITE-10878 fixes it by filtering cache descriptors and cache groups in
> GridCacheProcessor which is not generic solution.
> To fix the issue in a true generic way node should initialize its components
> (including cache processor) not on receiving NodeAdded message but
> NodeAddFinished message.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
