We are hosting Kafka on Kubernetes, and are facing configuration issues to ensure the stability of our operations. Kubernetes may cause dynamic restarts of the Kafka broker pods. After a restart, rebalancing and replication requires unpredictably more CPU resources than for normal operation, and consumer group committed offsets may get lost for some topic partitions. This results in redelivery of all messages currently stored in the message logs. We need to ensure that offsets do not get corrupted during broker restarts, while maintaining a feasible and cost-effective resource management
Hi there?
I read your project description carefully and I am really interested in your project.
I have professional knowledge and rich experiences in Kubernetes and I have already fixed similar issues before.
As I am a senior full stack developer, I will provide you 100% guaranteed products and you will feel happy from my results.
Hope your reply for more discussion soon.
Regards