You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Maxim Muzafarov (Jira)" <ji...@apache.org> on 2019/10/10 12:01:00 UTC

[jira] [Commented] (IGNITE-11468) System caches should not survive client reconnect

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

Maxim Muzafarov commented on IGNITE-11468:
------------------------------------------

Moved to the next release due to inactivity. Please, feel free to move it back if you will be able to complete the ticket by 2.8 code freeze date, December 2, 2019.


> System caches should not survive client reconnect
> -------------------------------------------------
>
>                 Key: IGNITE-11468
>                 URL: https://issues.apache.org/jira/browse/IGNITE-11468
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Alexey Goncharuk
>            Assignee: Dmitriy Govorukhin
>            Priority: Major
>             Fix For: 2.8
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> After IGNITE-10898 it became clear that system caches surviving client reconnect lead are error-prone: there are too many specific code paths leading to logic duplication and exclusions. At the same time, the benefit of system caches survival is not tangible.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)