Return-Path: X-Original-To: apmail-cloudstack-issues-archive@www.apache.org Delivered-To: apmail-cloudstack-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B3F8D101B7 for ; Thu, 5 Sep 2013 17:04:57 +0000 (UTC) Received: (qmail 99351 invoked by uid 500); 5 Sep 2013 17:04:55 -0000 Delivered-To: apmail-cloudstack-issues-archive@cloudstack.apache.org Received: (qmail 99315 invoked by uid 500); 5 Sep 2013 17:04:55 -0000 Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list issues@cloudstack.apache.org Received: (qmail 99080 invoked by uid 500); 5 Sep 2013 17:04:54 -0000 Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org Received: (qmail 99018 invoked by uid 99); 5 Sep 2013 17:04:54 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Sep 2013 17:04:54 +0000 Date: Thu, 5 Sep 2013 17:04:54 +0000 (UTC) From: "Murali Reddy (JIRA)" To: cloudstack-issues@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (CLOUDSTACK-4604) add cancel/restart/pause async jobs to help recovery from failures MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CLOUDSTACK-4604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Murali Reddy updated CLOUDSTACK-4604: ------------------------------------- Description: Two complementary functionalities want to address with this improvement. - checkpoint the async jobs. perhaps use current journal to record the all entity manipulation, For e.g asyncJob for VM create can have journal like Volume, create, ID Network, implement, id Nic, prepare, id etc - asyncjob management api currently exposes ability to perform query and list async jobs. There is no api support to cancel a job or restart a job. async job manager can be enhanced to add pause, cancel, restart the jobs A Job pause (pause to nearest checkpoint) and job restart (restart from the last checkpoint), cancel (rollback from last checkpoint) can be used to help recovering from failures. was: Two complementary functionalities want to address with the bug. - checkpoint the async jobs. perhaps use current journal to record the all entity manipulation, For e.g asyncJob for VM create can have journal like Volume, create, ID Network, implement, id Nic, prepare, id etc - asyncjob management api currently exposes ability to perform query and list async jobs. There is no api support to cancel a job or restart a job. async job manager can be enhanced to add pause, cancel, restart the jobs A Job pause (pause to nearest checkpoint) and job restart (restart from the last checkpoint), cancel (rollback from last checkpoint) can be used to help recovering from failures. > add cancel/restart/pause async jobs to help recovery from failures > ------------------------------------------------------------------ > > Key: CLOUDSTACK-4604 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4604 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the default.) > Reporter: Murali Reddy > Fix For: Future > > > Two complementary functionalities want to address with this improvement. > - checkpoint the async jobs. perhaps use current journal to record the all entity manipulation, For e.g asyncJob for VM create can have journal like > Volume, create, ID > Network, implement, id > Nic, prepare, id etc > - asyncjob management api currently exposes ability to perform query and list async jobs. There is no api support to cancel a job or restart a job. async job manager can be enhanced to add pause, cancel, restart the jobs > A Job pause (pause to nearest checkpoint) and job restart (restart from the last checkpoint), cancel (rollback from last checkpoint) can be used to help recovering from failures. -- 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