[IGNITE-2779] BinaryMarshaller caches must be cleaned during client reconnect.

• Type: Task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.5.0.final
• Fix Version/s: 2.3
• Component/s: cache, general
• Labels: community
• Assignee: Nikita Amelchev
• Reporter: Vladimir Ozerov
• Created: 09/Mar/16 09:15
• Updated: 04/Dec/17 08:25
• Resolved: 06/Sep/17 14:34

Description

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.

Issue Links

• is duplicated by: IGNITE-5794 BinaryMetadata is lost if all server nodes have been restarted
• links to: GitHub Pull Request #2518
• links to: Teamcity tests
• links to: Upsource