Apache Druid

image.png

try running with druid.indexer.tasklock.batchSegmentAllocation=true in the overlord config

<@U03BJAMQ4H5>, due to some other issues identified, can you help to confirm if the IP address in this line is coordinator?
```2023-02-22T21:25:47,394 WARN [task-runner-0-priority-0] org.apache.druid.indexing.common.IndexTaskClient - submitRequest failed for [<http://10.64.211.239:8100/druid/worker/v1/chat/index_parallel_mulesoft_long_query_d1_2_bmkknked_2023-02-22T17%3A54%3A09.474Z/segment/allocate>]```


you can check the services tab and see what port the corrdinator is running on

to answer your original question: `10.64.211.239:8100` would have been the main `index_parallel` task for your ingest job

the subtask calls `/segment/allocate` on the main task, then the main task hands it a segment ID

it's possible the main task failed for some reason and that's why you saw so many failures on the workers (the main task went away)

if you're having problems with native batch ingest, i suggest trying with SQL-based ingest via MSQ (<https://druid.apache.org/docs/latest/multi-stage-query/>)

It is much easier to debug! many errors don't happen at all due to better design. and the errors that do happen are collected and displayed more cleanly

Thx <@U0344FW86DD> for the explanation. Saved me a lot time to dig the code. The root cause is clear. We have a deployment which killed all the tasks.

ha! that'll do it! :slightly_smiling_face: