[
https://issues.apache.org/jira/browse/CLOUDSTACK-9195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15067747#comment-15067747
]
ASF GitHub Bot commented on CLOUDSTACK-9195:
--------------------------------------------
Github user koushik-das commented on the pull request:
https://github.com/apache/cloudstack/pull/1272#issuecomment-166552880
Steps to test:
- Prior to fix check for jobs in async_job table where job_status = 2 and
job_complete_msid is NULL.
- These entries won't get cleaned up even after "job.expire.minutes" global
config as part of GC thread.
- After the fix the entries should get cleaned up.
> Cancelled/failed async jobs not getting cleaned up from DB
> ----------------------------------------------------------
>
> Key: CLOUDSTACK-9195
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9195
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
> Affects Versions: 4.6.0, 4.7.0
> Reporter: Koushik Das
> Assignee: Koushik Das
> Fix For: 4.8.0
>
>
> Some cancelled/failed async jobs are not getting cleaned up from DB even
> after "job.expire.minutes". These jobs are marked as cancelled/failed when MS
> is restarted, check for 'job_status' as 2 (FAILED) and 'job_result' as "job
> cancelled because of management server restart or shutdown" in async_job
> table in DB. These are not getting cleaned as 'job_complete_msid' field is
> not set in DB.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
