[jira] [Updated] (IGNITE-1238) Joining node should be discarded in case discovery exchange data can't be deserialized

2017-09-25 Thread Vladimir Ozerov (JIRA) 

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

Vladimir Ozerov updated IGNITE-1238:

Fix Version/s: (was: 2.3)

> 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
>
> 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.4.14#64029)

[jira] [Updated] (IGNITE-1238) Joining node should be discarded in case discovery exchange data can't be deserialized

2017-07-10 Thread Vladimir Ozerov (JIRA) 

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

Vladimir Ozerov updated IGNITE-1238:

Fix Version/s: (was: 2.1)
   2.2

> 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
> Fix For: 2.2
>
>
> 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.4.14#64029)

[jira] [Updated] (IGNITE-1238) Joining node should be discarded in case discovery exchange data can't be deserialized

2017-04-10 Thread Vladimir Ozerov (JIRA) 

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

Vladimir Ozerov updated IGNITE-1238:

Fix Version/s: (was: 2.0)
   2.1

> 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: 2.1
>
>
> 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.15#6346)

[jira] [Updated] (IGNITE-1238) Joining node should be discarded in case discovery exchange data can't be deserialized

2016-11-17 Thread Vladimir Ozerov (JIRA) 

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

Vladimir Ozerov updated IGNITE-1238:

Fix Version/s: (was: 1.8)
   2.0

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

[jira] [Updated] (IGNITE-1238) Joining node should be discarded in case discovery exchange data can't be deserialized

2016-08-09 Thread Pavel Tupitsyn (JIRA) 

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

[jira] [Updated] (IGNITE-1238) Joining node should be discarded in case discovery exchange data can't be deserialized

2016-05-16 Thread Denis Magda (JIRA) 

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

Denis Magda updated IGNITE-1238:

Fix Version/s: (was: 1.6)
   1.7

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