cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-6740) Direct agent command throttling improvements
Date Thu, 22 May 2014 08:46:42 GMT

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

ASF subversion and git services commented on CLOUDSTACK-6740:
-------------------------------------------------------------

Commit 120da605b06e6cd5dc04c6d1eab9e10005bd6807 in cloudstack's branch refs/heads/4.4-forward
from [~koushikd]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=120da60 ]

CLOUDSTACK-6740: Direct agent command throttling improvements
List of changes:
1. Created a separate thread pool for handling cron and ping tasks. The size of the pool is
based on direct.agent.pool.size. The existing direct agent pool will run all commands other
than cron and ping.
2. For normal tasks (generated as part of user/admin API calls), if throttle limit is reached
then tasks get queued up for subsequent execution once threads are available.
3. For cron and ping tasks (internally generated by MS like ping, VM sync etc.), if throttle
limit is reached then these gets rejected. Since these are internally generated these can
be rejected without any issues.


> Direct agent command throttling improvements
> --------------------------------------------
>
>                 Key: CLOUDSTACK-6740
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6740
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.4.0
>            Reporter: Koushik Das
>            Assignee: Koushik Das
>             Fix For: 4.5.0
>
>
> List of changes:
> 1. Create a separate thread pool for handling cron tasks. Currently normal and cron tasks
are all handled by the same direct agent thread pool.
> 2. For normal tasks (generated as part of user/admin API calls), if throttle limit reached
then tasks will be queued up for subsequent execution. This will avoid uncertainty as to when
a certain command pass/fail based on the throttling. For now the queue is unbounded but this
needs to be revisited. One possibility is to change the agent state to something appropriate,
based on the queue limit, so that commands are not sent to this host from the upper layers
of MS.
> 3. For cron tasks (internally generated by MS like ping, VM sync etc.), if throttle limit
reached then it will be rejected. Since these are internally generated these can be rejected
without any issues.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message