[
https://issues.apache.org/jira/browse/IGNITE-2779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16141711#comment-16141711
]
ASF GitHub Bot commented on IGNITE-2779:
----------------------------------------
GitHub user NSAmelchev opened a pull request:
https://github.com/apache/ignite/pull/2518
IGNITE-2779 BinaryMarshaller caches must be cleaned during client reconnect.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/NSAmelchev/ignite IGNITE-2779
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/2518.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2518
----
commit 9170321182797ebb2acada407efea15421875911
Author: NSAmelchev <[email protected]>
Date: 2017-08-25T14:50:10Z
add test and fix
----
> 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.2
>
> 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)
