You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Pavel Tupitsyn (Jira)" <ji...@apache.org> on 2020/12/03 09:26:00 UTC

[jira] [Updated] (IGNITE-13496) Java thin: Use non-blocking socket IO

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

Pavel Tupitsyn updated IGNITE-13496:
------------------------------------
    Release Note: Java thin: async operations don't block user threads on write; IgniteClient uses one worker thread for all connections instead of a dedicated thread for every connection.

> Java thin: Use non-blocking socket IO 
> --------------------------------------
>
>                 Key: IGNITE-13496
>                 URL: https://issues.apache.org/jira/browse/IGNITE-13496
>             Project: Ignite
>          Issue Type: Improvement
>          Components: thin client
>    Affects Versions: 2.9
>            Reporter: Pavel Tupitsyn
>            Assignee: Pavel Tupitsyn
>            Priority: Major
>             Fix For: 2.10
>
>          Time Spent: 6.5h
>  Remaining Estimate: 0h
>
> IGNITE-7623 introduces async APIs to the Java thin client. However, socket writes still cause user thread blocking and thus reduce scalability.
> Investigate and prepare an IEP to use non-blocking IO.
> This ticket does not affect user-facing APIs, only changes the way we do IO internally.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)