[
https://issues.apache.org/jira/browse/IGNITE-11199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16762484#comment-16762484
]
Sergey Antonov commented on IGNITE-11199:
-----------------------------------------
[~6uest] I left fiew comments. Please fix it!
> Add extra logging for client-server connections in TCP discovery
> ----------------------------------------------------------------
>
> Key: IGNITE-11199
> URL: https://issues.apache.org/jira/browse/IGNITE-11199
> Project: Ignite
> Issue Type: Improvement
> Reporter: Ivan Rakov
> Assignee: Andrey Kalinin
> Priority: Major
> Time Spent: 50m
> Remaining Estimate: 0h
>
> When client node connects to a server node, it should print detailed
> information about server (at least, server node ID and consistent ID).
> When server node starts serving client node connection, it also should print
> detailed information about client.
> Currently, all we have is abstract logs about connections.
> On client side:
> {code:java}
> [2019-02-02 17:50:43,270][INFO
> ][grid-nio-worker-tcp-comm-0-#24][TcpCommunicationSpi] Established outgoing
> communication connection [locAddr=/127.0.0.1:53183, rmtAddr=/127.0.0.1:47100]
> [2019-02-02 17:50:43,446][INFO
> ][grid-nio-worker-tcp-comm-1-#25][TcpCommunicationSpi] Established outgoing
> communication connection [locAddr=/127.0.0.1:53184, rmtAddr=/127.0.0.1:47103]
> {code}
> On server side:
> {code:java}
> ./mahina98-2019-02-01.log:<190>Feb 1 18:24:19 mahina98.ca.sbrf.ru 2019-02-01
> 18:24:19.236[INFO
> ][tcp-disco-sock-reader-#5%DPL_GRID%DplGridNodeName%][o.a.i.s.d.tcp.TcpDiscoverySpi][tcp-disco-sock-reader-#5%DPL_GRID%DplGridNodeName%]
> Started serving remote node connection [rmtAddr=/10.124.133.5:56297,
> rmtPort=56297]
> {code}
> This is definetely not enough to find out which clients connected to local
> server node and to which server local client node has been connected.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
