cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rhtyd <...@git.apache.org>
Subject [GitHub] cloudstack pull request #1601: CLOUDSTACK-9348: Reduce Nio selector wait tim...
Date Fri, 01 Jul 2016 09:07:46 GMT
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>

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message