My Oracle Support Banner

ECE Resiliency To Temporary Broker Outage And Fully Kafka Cluster Outage (Doc ID 2984247.1)

Last updated on JANUARY 12, 2024

Applies to:

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

Goal

Scenario:

Elastic Charging Engine (ECE) is using Kafka as the backbone for all asynchronous messages for signaling, external and internal communication with Billing and Revenue Management (BRM).
Elastic Charging Server (ECS) are producing messages, and in case of one of the three broker outage (example rolling upgrade) at the time of writing which was the one holding lead partition for that messages, ECS tries to reconnect 6 times this broker during less than 2 minutes, and give up, leading to missing message within Kafka.

Kafka cluster is configured with 3 replica's topics, 127 partitions, and min-in-sync=2.

Requirement: ECS should be able to publish its message even having 2 broker running.
 

Solution

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
Goal
Solution
References


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