cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-9348) CloudStack Server degrades when a lot of connections on port 8250
Date Fri, 01 Jul 2016 09:08:11 GMT

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

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

GitHub user rhtyd opened a pull request:

    https://github.com/apache/cloudstack/pull/1601

    CLOUDSTACK-9348: Reduce Nio selector wait time

    This reduced the Nio loop selector wait time, this way the selector will
    check frequently (as much as 100ms per iteration) and handle any pending
    connection/tasks. This would make reconnections very quick at the expense of
    some CPU usage.
    
    /cc @swill @kiwiflyer guys can you please apply this fix in your env and test if you're
still able to produce any Nio related error b/w mgmt server(s) and kvm agent(s) not being
able to connect quickly. Please also watch out for any increased CPU usage (there should not
be any significant change), in which case we may increase the timeout from 100ms to 200-400ms.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/shapeblue/cloudstack nio-aggressive-selector

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/cloudstack/pull/1601.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1601
    
----
commit 0381b7ea185ef753873594216a67b8d376e3d658
Author: Rohit Yadav <rohit.yadav@shapeblue.com>
Date:   2016-07-01T09:02:58Z

    CLOUDSTACK-9348: Reduce Nio selector wait time
    
    This reduced the Nio loop selector wait time, this way the selector will
    check frequently (as much as 100ms per iteration) and handle any pending
    connection/tasks. This would make reconnections very quick at the expense of
    some CPU usage.
    
    Signed-off-by: Rohit Yadav <rohit.yadav@shapeblue.com>

----


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

Mime
View raw message