cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-5843) registering templates/isos should be either async or changed to non-blocking
Date Sat, 11 Jan 2014 01:13:50 GMT


ASF subversion and git services commented on CLOUDSTACK-5843:

Commit effa4c75b4970c1d87b2d1b0d83ae1f5e8312b0b in branch refs/heads/master from [~mlsorensen]
[;h=effa4c7 ]

For some reason the mgmt server is required to have access to the template
being registered in order to check its size against resource limits
during registration. This is bad, but worse, it's a sync call, so this
call can hang for up to the default HTTP connection timeout.

Reducing http timeout as a quick workaround, but this check needs to
1) be removed or 2) done later or 3)registerTemplate needs to be async
and 4) moved off the mgmt server (ssvm is the only thing that needs access to
template url).

> registering templates/isos should be either async or changed to non-blocking
> ----------------------------------------------------------------------------
>                 Key: CLOUDSTACK-5843
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.2.0, 4.3.0, 4.4.0
>            Reporter: Marcus Sorensen
>             Fix For: 4.4.0
> The call to register templates and isos does more than most sync calls do, it seems to
talk to the ssvm and have it run commands that can potentially time out. I ran into this in
a test system when we tried to register a template with a non-routable URL. The cloudstack
API call just hung. I realize that there was a problem (ssvm could not reach the template
host), but no sync call should do anything like this that would block.

This message was sent by Atlassian JIRA

View raw message