You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Pavel Tupitsyn (JIRA)" <ji...@apache.org> on 2016/08/09 12:33:32 UTC
[jira] [Updated] (IGNITE-1238) Joining node should be discarded in
case discovery exchange data can't be deserialized
[ https://issues.apache.org/jira/browse/IGNITE-1238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pavel Tupitsyn updated IGNITE-1238:
-----------------------------------
Fix Version/s: (was: 1.7)
1.8
> Joining node should be discarded in case discovery exchange data can't be deserialized
> --------------------------------------------------------------------------------------
>
> Key: IGNITE-1238
> URL: https://issues.apache.org/jira/browse/IGNITE-1238
> Project: Ignite
> Issue Type: Bug
> Components: general
> Affects Versions: 1.1.4
> Reporter: Valentin Kulichenko
> Assignee: Raúl Kripalani
> Priority: Critical
> Fix For: 1.8
>
>
> Currently a node will join even if unmarshalling fails (see {{TcpDiscoverySpi.onExchange()}} method, which can cause unexpected behaviour. For example, a continuous query listener is not deployed on some nodes in topology. Everything works, but some updates are lost. We should discard the node in this case and give a good error message to user with information on how to fix it properly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)