[
https://issues.apache.org/jira/browse/CLOUDSTACK-9195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15103719#comment-15103719
]
ASF GitHub Bot commented on CLOUDSTACK-9195:
--------------------------------------------
Github user DaanHoogland commented on the pull request:
https://github.com/apache/cloudstack/pull/1272#issuecomment-172323097
@koushik-das your change makes perfect sense to me from a db housekeeping
point of view. I have one (little) doubt; what are the semantic ramifications.
An asynchronous job might have continued after MS shutdown and its result might
be actually success or failure. I am not sure if diving into this field is
appropriate for this PR. Just checking with you as you might have already
considered it.
code LGTM
> 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)
