ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ignite TC Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-11159) Collections of 'start-on-join' caches and 'init-caches' should be filtered
Date Mon, 04 Feb 2019 14:51:00 GMT

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

Ignite TC Bot commented on IGNITE-11159:
----------------------------------------

{panel:title=--&gt; Run :: All: No blockers found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--&gt; Run :: All* Results|https://ci.ignite.apache.org/viewLog.html?buildId=2960479&amp;buildTypeId=IgniteTests24Java8_RunAll]

> Collections of 'start-on-join' caches and 'init-caches' should be filtered
> --------------------------------------------------------------------------
>
>                 Key: IGNITE-11159
>                 URL: https://issues.apache.org/jira/browse/IGNITE-11159
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Sergey Chugunov
>            Assignee: Sergey Chugunov
>            Priority: Major
>             Fix For: 2.8
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> IGNITE-10878 added filtering of cache descriptors when new node receives some additional
descriptors from cluster that dies before finishing new node join.
> It turned out there are additional collections in LocalJoinCachesContext that need to
be filtered.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message