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 Sun, 11 Sep 2016 11:10:20 GMT

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

Dmitry Karachentsev commented on IGNITE-3054:

* Fixed review notes except the first one, because GridNioSession is always the same: that
passed in onMessage() or used in right ClientNioMessageWorker.
* Fixed SPI tests (added new method to TcpDiscoverySpi to handle sending messages to Session).
* Some small fixes.
* Working on failing SSL tests, error happens during SSL handshake.

> 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