[
https://issues.apache.org/jira/browse/IGNITE-29004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18107122#comment-18107122
]
Ignite TC Bot commented on IGNITE-29004:
----------------------------------------
{panel:title=Branch: [pull/13507/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/13507/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=9302289&buildTypeId=IgniteTests24Java8_RunAll]
{color:#ffffff}tcbot-analysis-comment chainBuildId=9302289
rerunBuildIds=9302909,9302911,9302913{color}
> Refactor ClientImpl to use single instance of TcpDiscoveryIoSession per
> connection
> -----------------------------------------------------------------------------------
>
> Key: IGNITE-29004
> URL: https://issues.apache.org/jira/browse/IGNITE-29004
> Project: Ignite
> Issue Type: Task
> Reporter: Mikhail Petrov
> Assignee: Mikhail Petrov
> Priority: Major
> Labels: ise
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently, ClientImpl creates two separate sessions for a single connection
> to a server node:
> - org.apache.ignite.spi.discovery.tcp.ClientImpl.SocketWriter#setSocket
> - org.apache.ignite.spi.discovery.tcp.ClientImpl.SocketReader#setSocket
> We need to refactor this approach so that each session corresponds to exactly
> one connection to a remote node. This will allow us to encapsulate all
> P2P-related data associated with the connection within the session instance.
> This will allow us to eliminate the confusing SocketStream abstraction and
> rely solely on the session instance.
> NOTE:
> Currently, TcpDiscoveryIoSession is designed to be used in one direction
> only: either for reading from or writing to a socket. This is why two
> separate sessions are required on the client node side.
> We need to revise this approach and make a session responsible for
> communication in both directions. This will require introducing separate
> buffers for reading from and writing to the socket.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
