ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ignite TC Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-11784) Replace TcpDiscoveryNode to nodeId in TcpDiscoveryMessages
Date Fri, 12 Jul 2019 14:37:00 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-11784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16883861#comment-16883861
] 

Ignite TC Bot commented on IGNITE-11784:
----------------------------------------

{panel:title=--&gt; Run :: All: Possible Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Data Structures{color} [[tests 0 TIMEOUT , Exit Code |https://ci.ignite.apache.org/viewLog.html?buildId=4317312]]

{panel}
[TeamCity *--&gt; Run :: All* Results|https://ci.ignite.apache.org/viewLog.html?buildId=4317351&amp;buildTypeId=IgniteTests24Java8_RunAll]

> 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: Denis Chudov
>            Priority: Major
>             Fix For: 2.8
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> {{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.14#76016)

Mime
View raw message