[
https://issues.apache.org/jira/browse/IGNITE-1238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14731442#comment-14731442
]
Valentin Kulichenko commented on IGNITE-1238:
---------------------------------------------
Raul, you can use scenario described here to reproduce the issue:
https://issues.apache.org/jira/browse/IGNITE-1205. Just replace Visor with an
ordinary node started with {{ignite.sh}} (i.e., without additional classes on
classpath). This node will join topology, but it should not be able to do this.
> 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: ignite-1.4
>
>
> 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)
