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 Sat, 21 May 2016 08:48:12 GMT


ASF GitHub Bot commented on CLOUDSTACK-9348:

Github user rhtyd commented on the pull request:
    @swill if it's failing for addHost, can you send the mgmt server log, marvin log and the
agent log, and details of the environment (as much as possible). I can have a look at it tonight
or tomorrow morning. If it helps we can pair-debug the issue over GTM in your CI environment?
    It would also help if anyone else is able to reproduce the error on current master as
well, pinging @DaanHoogland @wido @nlivens @nvazquez @koushik-das @kiwiflyer and others.
    @swill if we're unable to fix the issue then sure we can revert it.

> 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