My Oracle Support Banner

How to Reset Kafka Offset in Case of Kafka Partition ID Conflicts (Doc ID 2984773.1)

Last updated on NOVEMBER 14, 2023

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

There is a known issue related to Kafka Partition ID conflicts, where issue is observed when two of the Diameter Gateways (DGW) also happened to have Kafka Consumer Groups consuming from the same partition ID. Due to this, DGWs heap usages increase quickly and become unresponsive, ultimately it can cause the Java Virtual Memory (JVM) to run out of memory and the Kafka notifications/messages backlog in DGW to increase.

How to resolve this issue? 

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


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