You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Alena Prokharchyk (JIRA)" <ji...@apache.org> on 2013/06/20 01:16:20 UTC

[jira] [Resolved] (CLOUDSTACK-1939) Job-Executor and StartCommand in sequence

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-1939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alena Prokharchyk resolved CLOUDSTACK-1939.
-------------------------------------------

    Resolution: Fixed

Fixed with d66e9c7b518895c28461118523698b6a7f0fd830
                
> Job-Executor and StartCommand in sequence
> -----------------------------------------
>
>                 Key: CLOUDSTACK-1939
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1939
>             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
>            Reporter: Jeronimo
>            Assignee: Alena Prokharchyk
>            Priority: Minor
>
> 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