[jira] [Commented] (CLOUDSTACK-1940) Job-Executor and StartCommand in sequence

["Nikita Gubenko (JIRA)" <ji...@apache.org>]

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

Nikita Gubenko commented on CLOUDSTACK-1940:
--------------------------------------------

Will this be reviewed in the near future? It's quite annoying thing while testing cloudstack for deploying lots of VMs
                
> Job-Executor and StartCommand in sequence
> -----------------------------------------
>
>                 Key: CLOUDSTACK-1940
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1940
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: API
>    Affects Versions: 4.0.0, 4.0.1, 4.1.0, 4.2.0
>            Reporter: Jeronimo
>              Labels: patch
>
> Hi List.
> I'm having issues when deploying a big number of virtual machines across a number of nodes.
> the imporession that i get ( from the logs) is that the AsyncJobExecutor is pulling jobs from the queue and do them one by one (which when you are deploying a big number of virtual machines could take a long while)
> After sending emails to the dev group they've asked me to open a BUG.
> Here more data:
> I can see the override on agent/api/StartCommand.java
> @Override
> public boolean executeInSequence() {
>       return true;                                                                                                                    
> }

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira