ECE Nodes Participating in Customer Load When They Should Not
(Doc ID 2459346.1)
Last updated on APRIL 08, 2021
Applies to:Oracle Communications BRM - Elastic Charging Engine - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
WorkManager threads has been assigned/executed in customerUpdater/customerLoader nodes instead of just Server charging nodes.
This has a side effect of skewing fetch/load balancing. Additionally, it is uncertain that even short lasting nodes could be accidentally assigned which meant for longer duration as well as the effect when one of these non 'proper' nodes may terminate before the work is done.
The reason that the customerLoader and customerUpdater are participating in the load is a bug in the implementation of the work manager – these threads should not be left executing in these processes. If one looks at the “role” in the ece_cluster_overview, only nodes of type “OracleCommunicationBrmChargingServerChargingLauncher” should be participating in the load. But one could notice that the WorkManager threads are running in the customerUpdater as well:
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document