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] [Commented] (IGNITE-2779) BinaryMarshaller caches must be cleaned during client reconnect.
Date Mon, 04 Sep 2017 12:42:00 GMT

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

Anton Vinogradov commented on IGNITE-2779:
------------------------------------------

[~NSAmelchev], 
Looks good to me.

[~vozerov],
Could you please make final review?

> BinaryMarshaller caches must be cleaned during client reconnect.
> ----------------------------------------------------------------
>
>                 Key: IGNITE-2779
>                 URL: https://issues.apache.org/jira/browse/IGNITE-2779
>             Project: Ignite
>          Issue Type: Task
>          Components: cache, general
>    Affects Versions: 1.5.0.final
>            Reporter: Vladimir Ozerov
>            Assignee: Amelchev Nikita
>              Labels: community
>             Fix For: 2.3
>
>         Attachments: IgniteProblemTest.java
>
>
> The problem is originally reported by Vinay Sharma here: http://apache-ignite-users.70518.x6.nabble.com/changed-cache-configuration-and-restarted-server-nodes-Getting-exception-td3064.html#none
> *Root cause*:
> When client is reconnected to topology after full topology restart (i.e. all server nodes
were down), it doesn't re-send binary metadata to topology. As a result, {{BinaryMarshaller}}
exception occurs.
> *Steps to reproduce*
> Run attached code.
> *Proposed solution*
> Clean cached binary metadata during re-connect.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message