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 Wed, 11 May 2016 14:21:12 GMT


ASF GitHub Bot commented on CLOUDSTACK-9348:

Github user kiwiflyer commented on the pull request:
    @rhtyd We're still seeing some odd behaviour related to the agent with this PR (and PR1534)
applied to 2 of our hardware labs. What we're seeing is 100% cpu on the agent (KVM). There's
nothing obvious in the debug logs indicating a problem. I've tried it both behind haproxy
and directly to the management server and we see the same symptoms. Let me know what we can
provide to help in terms of debugging.

> 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