ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dmitry Karachentsev (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-3054) Rework client connection handling from thread-per-client to NIO model.
Date Wed, 12 Oct 2016 08:27:21 GMT

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

Dmitry Karachentsev commented on IGNITE-3054:

Semen, thanks for review, added your recommendations to onDisconnected() method.

The case you worry about could happen only if message was received for disconnected client,
so we can simply drop it (I've added new check). This behavior is provided by connection logic
that will not add new worker if there was not stopped current one. Also I need access to worker
from listener, because there are operations that require to change it's state.

> Rework client connection handling from thread-per-client to NIO model.
> ----------------------------------------------------------------------
>                 Key: IGNITE-3054
>                 URL: https://issues.apache.org/jira/browse/IGNITE-3054
>             Project: Ignite
>          Issue Type: Task
>          Components: general
>    Affects Versions: 1.5.0.final
>            Reporter: Vladimir Ozerov
>            Assignee: Dmitry Karachentsev
>             Fix For: 1.8
> Currently both servers and clients has the same operational model - thread-per-connection.
While being more or less fine for servers, this could be a problem for clients when their
total number is too high (e.g. 1000 or even more).
> We should rework client handling model and employ standard NIO technique: one or several
acceptor threads + thread pool to server requests.

This message was sent by Atlassian JIRA

View raw message