ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Antonov (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (IGNITE-11784) Replace TcpDiscoveryNode to nodeId in TcpDiscoveryMessages
Date Thu, 25 Apr 2019 12:07:00 GMT

     [ 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 {{TcpDiscoveryNodesRing }} on target
node.   (was: {{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. )

> 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
>            Assignee: 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 {{TcpDiscoveryNodesRing }} on target node. 



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

Mime
View raw message