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

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

Github user rhtyd commented on the pull request:

    https://github.com/apache/cloudstack/pull/1549#issuecomment-220893971
  
    @swill I ran tests on latest master using packages: 
http://packages.shapeblue.com/cloudstack/custom/master-latest/
    
    I was able to deploy a zone with two KVM hosts and a mgmt server (on 
centos6). I was able to use a cloudmonkey based script and it was able to add 
multiple hosts without any error; here is the log and deploy script:
    
    
[cloudmonkey.log.txt](https://github.com/apache/cloudstack/files/276870/cloudmonkey.log.txt)
    
[deploy-kvm-adv.sh.txt](https://github.com/apache/cloudstack/files/276871/deploy-kvm-adv.sh.txt)
    
    @swill I was then able to launch VMs, see systemvm connect and perform 
regression tests. I'm unable to reproduce the issue now, I think master is 
stable; in case you hit the `addHost` issue please send me the mgmgt server and 
agent logs. Thanks.


> 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