This message was deleted.
# general
s
This message was deleted.
b
Check in the ingestion log if it is not able to connect to specific offset and waiting for that.
If for any reason offset is missed deleted from kafka and druid has not completed consuming it, it will wait. In that scenario, we should stop the ingestion, do HARD Reset of supervisor and start reading from first available offset from kafka. BY doing this you might loose the data from the offset druid was waiting and till the offset you have started now.
Before doing this make sure you are able to connect to kafka stream, you can check this by opening the supervisor in
open in dataloader
and by going to the
connect
tab.
h
is the ingestion log available in the druid ui?
b
yes, Druid console
Ingestion
tab
🙌 1
h
i got this when i tried to
open in dataloader
b
Check if your zookeeper is running fine and you are able to connect to the specific topic from outside , may be running a consumer command to read from the topic.
Also check if you have a stable overlord Leader. you may check the leader overlord log to see if you can find more info on the error
h
👍