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

Posted to issues@ignite.apache.org by "Mikhail Petrov (Jira)" <ji...@apache.org> on 2026/09/04 07:13:00 UTC

[jira] [Assigned] (IGNITE-29006) Refactor TcpDiscoveryMessageSerializer to handle serialization only

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

Mikhail Petrov reassigned IGNITE-29006:
---------------------------------------

    Assignee: Mikhail Petrov

> Refactor TcpDiscoveryMessageSerializer to handle serialization only
> -------------------------------------------------------------------
>
>                 Key: IGNITE-29006
>                 URL: https://issues.apache.org/jira/browse/IGNITE-29006
>             Project: Ignite
>          Issue Type: Task
>            Reporter: Mikhail Petrov
>            Assignee: Mikhail Petrov
>            Priority: Major
>              Labels: ise
>             Fix For: 2.19
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> We need to refactor TcpDiscoveryMessageSerializer so that it only encapsulates TCP Discovery message serialization logic.
> It is proposed that TcpDiscoveryIoSession hold a TcpDiscoveryMessageSerializer instance instead of having TcpDiscoveryMessageSerializer extend the session.
> NOTE: Currently, two threads can access the Discovery IO session for writing: SocketReader and ClientMessageWorker. This can only occur on the server side.
> Concurrent writes to the same session may corrupt message serialization because messages are currently serialized and written in batches (see  TcpDiscoveryIoSession#writeMessage).



--
This message was sent by Atlassian Jira
(v8.20.10#820010)