Koushik Das created CLOUDSTACK-8425:
---------------------------------------
Summary: Job framework: Same internal job can execute
simultaneously
Key: CLOUDSTACK-8425
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8425
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Management Server
Affects Versions: 4.5.0
Reporter: Koushik Das
Assignee: Koushik Das
Priority: Critical
Fix For: 4.6.0
Same internal work job can be executed simultaneously by 2 worker threads. The
below logs show that the same work job-24152 is executed by threads
Work-Job-Executor-84 and Work-Job-Executor-85. This can lead to undesired
behaviour subsequently.
2015-03-17 14:43:34,289 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(API-Job-Executor-12:ctx-4fa08ed6 job-24151 ctx-f7582544) (logid:26c78006) Sync
job-24152 execution on object VmWorkJobQueue.1396
2015-03-17 14:43:35,420 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(AsyncJobMgr-Heartbeat-1:ctx-4dc28af0) (logid:b0db94c2) Schedule queued
job-24152
2015-03-17 14:43:35,422 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(Work-Job-Executor-83:ctx-62660b07 job-24149/job-24150) (logid:97d686aa)
Schedule queued job-24152
2015-03-17 14:43:35,426 INFO [o.a.c.f.j.i.AsyncJobMonitor]
(Work-Job-Executor-84:ctx-9568eb6e job-24151/job-24152) (logid:d28187a4) Add
job-24152 into job monitoring
2015-03-17 14:43:35,428 INFO [o.a.c.f.j.i.AsyncJobMonitor]
(Work-Job-Executor-85:ctx-5a06c91e job-24151/job-24152) (logid:e55e3f25) Add
job-24152 into job monitoring
2015-03-17 14:43:35,432 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(Work-Job-Executor-84:ctx-9568eb6e job-24151/job-24152) (logid:26c78006)
Executing AsyncJobVO
{id:24152, userId: 4, accountId: 4, instanceType: null, instanceId: null, cmd:
com.cloud.vm.VmWorkDetachVolume, cmdInfo:
rO0ABXNyAB9jb20uY2xvdWQudm0uVm1Xb3JrRGV0YWNoVm9sdW1lhvReA-s81AMCAAFMAAh2b2x1bWVJZHQAEExqYXZhL2xhbmcvTG9uZzt4cgATY29tLmNsb3VkLnZtLlZtV29ya5-ZtlbwJWdrAgAESgAJYWNjb3VudElkSgAGdXNlcklkSgAEdm1JZEwAC2hhbmRsZXJOYW1ldAASTGphdmEvbGFuZy9TdHJpbmc7eHAAAAAAAAAABAAAAAAAAAAEAAAAAAAABXR0ABRWb2x1bWVBcGlTZXJ2aWNlSW1wbHNyAA5qYXZhLmxhbmcuTG9uZzuL5JDMjyPfAgABSgAFdmFsdWV4cgAQamF2YS5sYW5nLk51bWJlcoaslR0LlOCLAgAAeHAAAAAAAAALWw,
cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
null, initMsid: 104230524961057, completeMsid: null, lastUpdated: null,
lastPolled: null, created: Tue Mar 17 14:43:34 EDT 2015}
2015-03-17 14:43:35,432 DEBUG [c.c.v.VmWorkJobDispatcher]
(Work-Job-Executor-84:ctx-9568eb6e job-24151/job-24152) (logid:26c78006) Run VM
work job: com.cloud.vm.VmWorkDetachVolume for VM 1396, job origin: 24151
2015-03-17 14:43:35,433 DEBUG [c.c.v.VmWorkJobHandlerProxy]
(Work-Job-Executor-84:ctx-9568eb6e job-24151/job-24152 ctx-0f9cd10a)
(logid:26c78006) Execute VM work job: com.cloud.vm.VmWorkDetachVolume
{"volumeId":2907,"userId":4,"accountId":4,"vmId":1396,"handlerName":"VolumeApiServiceImpl"}
2015-03-17 14:43:35,435 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(Work-Job-Executor-85:ctx-5a06c91e job-24151/job-24152) (logid:26c78006)
Executing AsyncJobVO
{id:24152, userId: 4, accountId: 4, instanceType: null, instanceId: null, cmd:
com.cloud.vm.VmWorkDetachVolume, cmdInfo:
rO0ABXNyAB9jb20uY2xvdWQudm0uVm1Xb3JrRGV0YWNoVm9sdW1lhvReA-s81AMCAAFMAAh2b2x1bWVJZHQAEExqYXZhL2xhbmcvTG9uZzt4cgATY29tLmNsb3VkLnZtLlZtV29ya5-ZtlbwJWdrAgAESgAJYWNjb3VudElkSgAGdXNlcklkSgAEdm1JZEwAC2hhbmRsZXJOYW1ldAASTGphdmEvbGFuZy9TdHJpbmc7eHAAAAAAAAAABAAAAAAAAAAEAAAAAAAABXR0ABRWb2x1bWVBcGlTZXJ2aWNlSW1wbHNyAA5qYXZhLmxhbmcuTG9uZzuL5JDMjyPfAgABSgAFdmFsdWV4cgAQamF2YS5sYW5nLk51bWJlcoaslR0LlOCLAgAAeHAAAAAAAAALWw,
cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
null, initMsid: 104230524961057, completeMsid: null, lastUpdated: null,
lastPolled: null, created: Tue Mar 17 14:43:34 EDT 2015}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
