[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15294424#comment-15294424
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9348:
--------------------------------------------

Github user swill commented on the pull request:

    https://github.com/apache/cloudstack/pull/1549#issuecomment-220735448
  
    @rhtyd uggg...  The first two builds on master after merging this back in 
have both resulted in the `addHost` error.  :(  Let me know what you need to 
troubleshoot this.  I have a couple PRs I want to do a final round of testing 
on, so I will try to get them tested and we will see if they also run into this 
issue when I try to test them.  If they do, I may have to revert again.  I am 
trying my best to get a bunch of the PRs that are close in, so I am pushing the 
freeze date a bit (obviously).  I will probably freeze over the weekend or 
early next week.  I would like to make sure we have this resolved though.  I 
don't want this to derail my final testing.  I will launch a bunch more CI 
right now and we will see how things go...


> 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)

Reply via email to