[
https://issues.apache.org/jira/browse/CLOUDSTACK-9348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15353107#comment-15353107
]
ASF GitHub Bot commented on CLOUDSTACK-9348:
--------------------------------------------
Github user swill commented on the issue:
https://github.com/apache/cloudstack/pull/1549
This was shared in the "4.9/master Testing Coordination" thread. Simon
Weller and his team at ENA have run into this on the latest master in both of
their hardware labs while testing master for me in preparation for the 4.9 RC.
I am still getting the `addHost` issue periodically which showed up a lot
when this had bigger issues.
I am concerned about this in production to be honest. How long has this
been running in production at your client?
> CloudStack Server degrades when a lot of connections on port 8250
> -----------------------------------------------------------------
>
> Key: CLOUDSTACK-9348
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9348
> 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:
> https://github.com/apache/cloudstack/blob/master/utils/src/main/java/com/cloud/utils/nio/NioConnection.java#L125
> 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
(v6.3.4#6332)
