You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Sergey Antonov (JIRA)" <ji...@apache.org> on 2019/04/18 16:36:00 UTC

[jira] [Updated] (IGNITE-11784) Replace TcpDiscoveryNode to nodeId in TcpDiscoveryMessages

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

Sergey Antonov updated IGNITE-11784:
------------------------------------
    Description: {{TcpDiscoveryDuplicateIdMessage}} and {{TcpDiscoveryStatusCheckMessage}} have TcpDiscoveryNode field. TcpDiscoveryNode could be huge object due to node attributes. We could sent only nodeId and get TcpDiscoveryNode from DiscoCache on target node.   (was: {{TcpDiscoveryDuplicateIdMessage}} and {{TcpDiscoveryStatusCheckMessage}} have TcpDiscoveryNode filed. TcpDiscoveryNode could be huge object due to node attributes. We could sent only nodeId and get TcpDiscoveryNode from DiscoCache on target node. )

> Replace TcpDiscoveryNode to nodeId in TcpDiscoveryMessages
> ----------------------------------------------------------
>
>                 Key: IGNITE-11784
>                 URL: https://issues.apache.org/jira/browse/IGNITE-11784
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Sergey Antonov
>            Priority: Major
>             Fix For: 2.8
>
>
> {{TcpDiscoveryDuplicateIdMessage}} and {{TcpDiscoveryStatusCheckMessage}} have TcpDiscoveryNode field. TcpDiscoveryNode could be huge object due to node attributes. We could sent only nodeId and get TcpDiscoveryNode from DiscoCache on target node. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)