[jira] [Updated] (IGNITE-11290) History of server node IDs should be passed to new nodes with NodeAddedMessage

2020-07-03 Thread Aleksey Plekhanov (Jira)


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

Aleksey Plekhanov updated IGNITE-11290:
---
Fix Version/s: (was: 2.9)

> History of server node IDs should be passed to new nodes with NodeAddedMessage
> --
>
> Key: IGNITE-11290
> URL: https://issues.apache.org/jira/browse/IGNITE-11290
> Project: Ignite
>  Issue Type: Bug
>Reporter: Sergey Chugunov
>Assignee: Sergey Chugunov
>Priority: Major
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> As part of IGNITE-5569 (bounded) history of IDs of all server nodes existed 
> in the cluster is introduced to prevent join requests with duplicate IDs if 
> network glitch happens during node's join process.
> Initial implementation maintains the history locally on each node and isn't 
> transferred to successfully joined nodes.
> It is needed to pass it (in NodeAdded messages) to new nodes to cover 
> edge-case scenarios of coordinator failover.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (IGNITE-11290) History of server node IDs should be passed to new nodes with NodeAddedMessage

2019-12-02 Thread Maxim Muzafarov (Jira)


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

Maxim Muzafarov updated IGNITE-11290:
-
Fix Version/s: (was: 2.8)
   2.9

> History of server node IDs should be passed to new nodes with NodeAddedMessage
> --
>
> Key: IGNITE-11290
> URL: https://issues.apache.org/jira/browse/IGNITE-11290
> Project: Ignite
>  Issue Type: Bug
>Reporter: Sergey Chugunov
>Assignee: Sergey Chugunov
>Priority: Major
> Fix For: 2.9
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> As part of IGNITE-5569 (bounded) history of IDs of all server nodes existed 
> in the cluster is introduced to prevent join requests with duplicate IDs if 
> network glitch happens during node's join process.
> Initial implementation maintains the history locally on each node and isn't 
> transferred to successfully joined nodes.
> It is needed to pass it (in NodeAdded messages) to new nodes to cover 
> edge-case scenarios of coordinator failover.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)