When kafka consumers are subscribing to a topic, as and when messages are produced, they are consumed by the consumers. But due to high traffic or latency or high load issues, there would be a lag in consuming the messages.
Status of offsets of consumer groups are stored on Kafka broker. If that should be reset, for ex based on a duration ./bin/kafka-consumer-groups --bootstrap-server kafkaserver:9092 --group consumergroupname --reset-offsets --by-duration 1522760000 --execute If that should be reset, for ex based on
With curl commands, schemas can be retrieved/updated to Confluent SchemaRegistry. Get the latest schema available on the topic: curl -X GET http://localhost:8081/subjects/testtopic-value/versions/latest Get Schema compatibility: curl -X GET http://localhost:8081/config/testtopic-value Get versions of all registered schemas on a topic: curl -X