JRob
05/13/2025, 11:20 PM2025-05-13T23:09:59,308 INFO [task-runner-0-priority-0] org.apache.kafka.clients.consumer.internals.AbstractFetch - [Consumer clientId=consumer-kafka-supervisor-bmcfdhbl-1, groupId=kafka-supervisor-bmcfdhbl] Fetch position FetchPosition{offset=1189300635, offsetEpoch=Optional.empty, currentLeader=LeaderAndEpoch{leader=Optional[kafka-broker:9092 (id: 1691 rack: null)], epoch=absent}} is out of range for partition datasource-124, raising error to the application since no reset policy is configured
2025-05-13T23:09:59,308 WARN [task-runner-0-priority-0] org.apache.druid.indexing.kafka.IncrementalPublishingKafkaIndexTaskRunner - OffsetOutOfRangeException with message [Fetch position FetchPosition{offset=1189300635, offsetEpoch=Optional.empty, currentLeader=LeaderAndEpoch{leader=Optional[kafka-broker:9092 (id: 1691 rack: null)], epoch=absent}} is out of range for partition datasource-124]
2025-05-13T23:09:59,309 WARN [task-runner-0-priority-0] org.apache.druid.indexing.kafka.IncrementalPublishingKafkaIndexTaskRunner - Retrying in 30000ms
What I'm wondering is why isn't the Supervisor reporting the error? The job just gets stuck in an infinite loop...John Kowtko
05/14/2025, 1:27 AMJRob
05/14/2025, 3:02 PMIf set to^ this is the behaviour we want but it doesn't appear to be working, Druid surfaces the exception causing tasks to fail and ingestion to halt.false
JRob
05/14/2025, 3:02 PMLucas Capistrant
05/14/2025, 3:45 PMsupervisor section. Probably because they are shared across different streaming types. https://druid.apache.org/docs/29.0.1/ingestion/supervisor 29.0.1 docs still state that tasks should fail.Lucas Capistrant
05/14/2025, 4:01 PMJRob
05/14/2025, 10:27 PM