Description
When cluster entity is submitted via prism/server, logs say the following :
2015-10-07 05:33:19,430 INFO - [9959671@qtp-366590980-417 - 0bb0452f-1751-4017-a776-c6301aa737d4:pragya:POST//entities/submit/cluster] ~ Parsed Entity: A4dcc0afc-926620cf (EntityParser:94) 2015-10-07 05:33:19,431 INFO - [9959671@qtp-366590980-417 - 0bb0452f-1751-4017-a776-c6301aa737d4:pragya:POST//entities/submit/cluster] ~ Lock obtained for schedule/update of (cluster) A4dcc0afc-926620cf by 9959671@qtp-366590980-417 - 0bb0452f-1751-4017-a776-c6301aa737d4 (MemoryLocks:54) 2015-10-07 05:33:19,431 INFO - [9959671@qtp-366590980-417 - 0bb0452f-1751-4017-a776-c6301aa737d4:pragya:POST//entities/submit/cluster] ~ Successfully released lock for (cluster) A4dcc0afc-926620cf by 9959671@qtp-366590980-417 - 0bb0452f-1751-4017-a776-c6301aa737d4 (MemoryLocks:70) 2015-10-07 05:33:19,431 INFO - [9959671@qtp-366590980-417 - 0bb0452f-1751-4017-a776-c6301aa737d4:pragya:POST//entities/submit/cluster] ~ All update locks released for A4dcc0afc-926620cf (AbstractEntityManager:357)
As the logs suggest, lock is obtained for schedule/update of cluster which is not very intuitive.
Attachments
Attachments
Issue Links
- links to