[
https://issues.apache.org/jira/browse/CLOUDSTACK-7833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14201234#comment-14201234
]
Marcus Sorensen commented on CLOUDSTACK-7833:
---------------------------------------------
I'd like to see more info on this. What impact does it have? What triggers it?
I've seen this on occasion when vms fail, and I'm not sure if the vm is failing
due to this or if it is just something that doesn't matter.
> VM Async work jobs log "Was unable to find lock for the key vm_instance"
> errors at warn
> ---------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-7833
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7833
> 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
>
>
> When Deploy VM API is processed by the VM orchestration logic, VM Work jobs
> are created and put in the async job queue.
> While processing these jobs, log shows a lot of WARN statements as follows
> 2014-10-28 08:09:13,633 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (API-Job-Executor-100:ctx-e10c4339 job-464 ctx-4d5301e4) Sync job-726
> execution on object VmWorkJobQueue.286
> 2014-10-28 08:09:13,640 WARN [c.c.u.d.Merovingian2]
> (API-Job-Executor-100:ctx-e10c4339 job-464 ctx-4d5301e4) Was unable to find
> lock for the key vm_instance286 and thread id 1581663601
> 2014-10-28 08:18:32,003 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (API-Job-Executor-100:ctx-e10c4339 job-464 ctx-4d5301e4) Sync job-1332
> execution on object VmWorkJobQueue.286
> 2014-10-28 08:18:32,006 WARN [c.c.u.d.Merovingian2]
> (API-Job-Executor-100:ctx-e10c4339 job-464 ctx-4d5301e4) Was unable to find
> lock for the key vm_instance286 and thread id 1581663601
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
