You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2016/04/28 09:32:12 UTC
[jira] [Updated] (IGNITE-3054) Rework client connection handling
from thread-per-client to NIO model.
[ https://issues.apache.org/jira/browse/IGNITE-3054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vladimir Ozerov updated IGNITE-3054:
------------------------------------
Fix Version/s: (was: 1.6)
1.7
> 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
> Priority: Blocker
> Fix For: 1.7
>
>
> 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
(v6.3.4#6332)