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

Sergey Chugunov edited comment on IGNITE-5794 at 8/3/17 11:41 AM:
------------------------------------------------------------------

Correct fix for this issue is to clean up all metadata on client when it 
reconnects to the cluster. 

Sending metadata from client to server is dangerous as client node may 
disconnect from one cluster and connect to a completely different. Binary 
metadata cache in new cluster will be polluted by reconnected client.

The issue affects versions older than 2.0 but in 2.0+ it is more visible 
because of NPE.

However workaround to fix it is simple and requires only restarting client node 
on event of reconnect.


was (Author: sergey-chugunov):
Correct fix for this issue is to clean up all metadata on client when it 
reconnects to the cluster. 
Sending metadata from client to server is dangerous as client node may 
disconnect from one cluster and connect to a completely different. Binary 
metadata cache in new cluster will be polluted by reconnected client.

The issue affects versions older than 2.0 but in 2.0+ it is more visible 
because of NPE.

However workaround to fix it is simple and requires only restarting client node 
on event of reconnect.

> BinaryMetadata is lost if all server nodes have been restarted
> --------------------------------------------------------------
>
>                 Key: IGNITE-5794
>                 URL: https://issues.apache.org/jira/browse/IGNITE-5794
>             Project: Ignite
>          Issue Type: Bug
>          Components: binary, general
>    Affects Versions: 2.1
>            Reporter: Ilya Lantukh
>
> Steps to reproduce are described here: 
> http://apache-ignite-users.70518.x6.nabble.com/Problem-with-Messages-after-client-reconnect-td15127.html#none
> This problem occurs because client has metadata in it's local metadata cache 
> and decides that server node should have it too. But server lost it after 
> restart.
> Possible fixes:
> - Make client nodes re-send all contents of local metadata cache after 
> reconnect.
> - If node doesn't have metadata to process incoming message, it should 
> request it from sender node.



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

Reply via email to