ECE Is Not Come Back to UsageProcessing Automatically When K8S Cluster Is Getting Bounced
(Doc ID 2889407.1)
Last updated on FEBRUARY 23, 2023
Applies to:Oracle Communications BRM - Elastic Charging Engine - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
On Oracle Communications Elastic Charging Engine (ECE), 220.127.116.11.5 version, Cloud Native Deployment (CNE),
Sometimes, due to maintenance activity or due to disruption Kubernetes (K8S) cluster is going down and started up automatically, ECE is also going down and starting up. But ECE is not coming back to usageProcessing state.
1 .Setup ECE 18.104.22.168.5 CNE.
2. Restart the K8S cluster by bouncing all the worker-nodes.
3. Check if all the ECS pods have come up.
ECE is not coming back to usageProcessing state untill and unless the configLoader is started manually.
Though it is using ECE-Database as persistence, ECE is expecting the configloader job to be re-initiated manually to change its state to configDataLoaded after restart.
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