ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Raúl Kripalani (JIRA) <j...@apache.org>
Subject [jira] [Assigned] (IGNITE-1238) Joining node should be discarded in case discovery exchange data can't be deserialized
Date Mon, 31 Aug 2015 23:31:46 GMT

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

Raúl Kripalani reassigned IGNITE-1238:
--------------------------------------

    Assignee: Raúl Kripalani  (was: Valentin Kulichenko)

> 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)

Mime
View raw message