-
Task
-
Resolution: Won't Do
-
Medium
-
None
See stability runs documentation
There has been a degradation of performance observed in this release
when compared with the previous one.
Approximately 1% of transactions were not completed as expected for
some use cases. Average Execution Times are extended as well.
The unexpected results seem to point in the direction of the
interactions of the distributed locking feature with the database.
These areas as well as the conditions for the test need to be investigated
further.
# Common pattern in the audit.log for unexpected transaction completions a8d637fc-a2d5-49f9-868b-5b39f7befe25||ControlLoop-vFirewall-d0a1dfc6-94f5-4fd4-a5b5-4630b438850a|
policy:usecases:[org.onap.policy.drools-applications.controlloop.common:controller-usecases:1.9.0:usecases]|
2021-10-12T19:48:02.052+00:00|2021-10-12T19:48:02.052+00:00|0|
null:operational.modifyconfig.EVENT.MANAGER.FINAL:1.0.0|dev-policy-drools-pdp-0|
ERROR|400|Target Lock was lost|||VNF.generic-vnf.vnf-name||dev-policy-drools-pdp-0||
dev-policy-drools-pdp-0|microservice.stringmatcher|
{vserver.prov-status=ACTIVE, vserver.is-closed-loop-disabled=false,
generic-vnf.vnf-name=fw0002vm002fw002, vserver.vserver-name=OzVServer}||||
INFO|Session org.onap.policy.drools-applications.controlloop.common:controller-usecases:1.9.0:usecases| # The "Target Lock was lost" is a common message error in the unexpected results.