You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Amelchev Nikita (JIRA)" <ji...@apache.org> on 2017/09/07 07:08:00 UTC

[jira] [Updated] (IGNITE-5794) BinaryMetadata is lost if all server nodes have been restarted

     [ https://issues.apache.org/jira/browse/IGNITE-5794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Amelchev Nikita updated IGNITE-5794:
------------------------------------
    Attachment: IgniteClientReconnectMessagingTest.java

> 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
>            Assignee: Amelchev Nikita
>         Attachments: IgniteClientReconnectMessagingTest.java
>
>
> 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)