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

Dmitry Karachentsev commented on IGNITE-3054:
---------------------------------------------

Fixed race, but haven't found the root case of restart suites overtime. The 
same issues can be observed on master too, f.e. that tests terminated by 
timeout and sometimes they couldn't be stopped due to uninterruptible wait. No 
new failures found.

> 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
(v6.3.4#6332)

Reply via email to