cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-9348) CloudStack Server degrades when a lot of connections on port 8250
Date Thu, 05 May 2016 20:44:12 GMT


ASF GitHub Bot commented on CLOUDSTACK-9348:

Github user swill commented on the pull request:
    I confirmed that reverting this PR locally does fix my DeployDatacenter issues.
    I did an initial test with #1534 and it did get past the DeployDatacenter phase and started
testing, but it did not run the Nio tests (apparently it only runs that test sometimes?).
 I stopped that run and cleaned everything up and am running the CI against #1534 again to
see if I can get it to run the tests (and pass) and also come back with a clean CI run.  I
will update that PR with the status later tonight.
    Thanks for looking into this quickly to unblock our ability to do CI.  👍 

> CloudStack Server degrades when a lot of connections on port 8250
> -----------------------------------------------------------------
>                 Key: CLOUDSTACK-9348
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>            Reporter: Rohit Yadav
>            Assignee: Rohit Yadav
>             Fix For: 4.9.0
> An intermittent issue was found with a large CloudStack deployment, where servers could
not keep agents connected on port 8250.
> All connections are handled by accept() in NioConnection:
> A new connection is handled by accept() which does blocking SSL handshake. A good fix
would be to make this non-blocking and handle expensive tasks in separate threads/pool. This
way the main IO loop won't be blocked and can continue to serve other agents/clients.

This message was sent by Atlassian JIRA

View raw message