[
https://issues.apache.org/jira/browse/CLOUDSTACK-7628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14147178#comment-14147178
]
Min Chen commented on CLOUDSTACK-7628:
--------------------------------------
This is caused by a bug in code to set search criteria bind value, mismatched
with the bind parameter defined earlier, thus cut date criteria is not used.
> VM Worker job should be expunged one hour after completion instead of
> currently being expunged whenever cleanup task thread is run.
> -----------------------------------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-7628
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7628
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
> Affects Versions: 4.3.0
> Reporter: Min Chen
> Assignee: Min Chen
> Priority: Critical
> Fix For: 4.5.0
>
>
> Based on design, when VM worker job cleanup thread runs, it should only
> expunge those vm work jobs that are completed more than one hour ago. This is
> to prevent some Db constraint error in expunging these jobs since there are
> still reference to the worker job in async_job_map table. Also on some racing
> condition, we will encounter NPE due to removal of such jobs too quickly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
