My Oracle Support Banner

CNE ECE Does Not Specify Coherence Journaling-config In Helm Charts (Doc ID 2768407.1)

Last updated on APRIL 16, 2021

Applies to:

Oracle Communications BRM - Elastic Charging Engine - Version and later
Information in this document applies to any platform.


Coherence heavily uses Elastic Data feature called Flash journal. In Cloud Native(CN) Elastic Charging Engine (ECE) this leads to two problems:
 1. By default, journaling-config is not configured. It means that flash-journal data is stored into /tmp (a folder inside ECS container). Also, size is not defined which can lead to unlimited growth.
 2. Flash journal data should be persisted even across Pod restarts. I.e. if there is a Federation backlog and not-yet-replicated data is stored into the journal, this data MUST NOT be lost until fully consumed.
In order to avoid above mentioned problems following improvements are needed in CN ECE:
 - extend Helm charts to enable as a configuration variable.
  This location should be made an external storage (K8s Persistent Volume) as it has to survive Pod restarts and must be available for Event Charging Server(ECS) regardless of the worker node
 - high-journal-size should be at least configured (hard coded) to a recommended value


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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.