cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-9652) Job framework - Cancelling async jobs
Date Thu, 15 Dec 2016 17:52:58 GMT


ASF GitHub Bot commented on CLOUDSTACK-9652:

Github user karuturi commented on the issue:
    @marcaurele The thread which is running the job gets killed due to OperationCancelledException.
But, if any command is already sent and is being executed on hypervisor, that wont be cancelled.
check for the changes in AgentAttache where this new exception is thrown.
    For example, if a deployvm is cancelled and the command is already sent to hypervisor,
the vm will continue to launch on hypervisor. but, on cloudstack side, the threads and the
jobs will be cleanedup and cancelled. Eventually, vm sync will sync the states. There can
be instances when the job cancellation was successful but, the vm is in running state after
    The cancellation should be used with caution only by admin keeping in mind that some resource
cleanup on hypervisor might be required. 
    This will only unblock the jobs in cloudstack which are waiting for a long time for a
certain job to complete.

> Job framework - Cancelling async jobs
> -------------------------------------
>                 Key: CLOUDSTACK-9652
>                 URL:
>             Project: CloudStack
>          Issue Type: Improvement
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>            Reporter: Rajani Karuturi
>            Assignee: Rajani Karuturi
> enable cancellation of long running or subsequent queued up async jobs

This message was sent by Atlassian JIRA

View raw message