[jira] [Commented] (CLOUDSTACK-5843) registering templates/isos should be either async or changed to non-blocking

["Marcus Sorensen (JIRA)" <ji...@apache.org>]

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

Marcus Sorensen commented on CLOUDSTACK-5843:
---------------------------------------------

Looking at the code, it looks like it sends a command to the secondary storage vm agent, which does a bunch of things (creates directory on the nfs secondary storage to store the template, interrogates the remote url for things like download size, etc) before jumping into a thread to do the download and returning the sync command. It seems like this should be made async, and that's probably easier rather than trying to keep it from doing those things before returning.

> registering templates/isos should be either async or changed to non-blocking
> ----------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-5843
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5843
>             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
(v6.1.5#6160)