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 Mon, 02 May 2016 21:52:12 GMT


ASF GitHub Bot commented on CLOUDSTACK-9348:

Github user kiwiflyer commented on the pull request:
    I pulled this into a hardware lab on 4.8.1.  I setup a number of fake clients and hammered
8250. Prior to the patch the agents end up in a disconnected state after a few minutes.
    I applied the patch and my little DOS test is unable to affect the connectivity between
the management server and the agents.
    I also tested some provisioning activities and made sure the agent survived taking the
management server down and then bringing it back up.

> 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