As an analysis for an issue I had to write a simple java web socket client site code connecting to a Spring based application on the server side with a stomp based web socket broker .
Identifying Hidden Kafka Consumer after re-balance
We started noticing that at times we would get re-balance Kafka consumer group and suddenly we would notice our application consumer stop getting messages . And then before we could run some diagnostics it would re-balance again and our consumer would start getting messages but we would have lost some messages in between .
Read data till Kafka Consumer Committed Position
Making Kafka Consumer only read messages till a specified position .Specially to the point where another consumer stopped reading .