[
https://issues.apache.org/jira/browse/CLOUDSTACK-9652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15797138#comment-15797138
]
ASF GitHub Bot commented on CLOUDSTACK-9652:
--------------------------------------------
Github user karuturi commented on the issue:
https://github.com/apache/cloudstack/pull/1832
@rhtyd I dont buy that argument. Just for the ease of revert or cherry-pick
we shouldnt commit all the changes together. The revert or cherry-pick quickly
becomes irrelevant as more code gets committed on top of it. I would like to
commit them as is.
regarding the conflicts, will resolve them as soon as I get time. right
now, busy with $dayjob.
> Job framework - Cancelling async jobs
> -------------------------------------
>
> Key: CLOUDSTACK-9652
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9652
> 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
(v6.3.4#6332)
