Apache Druid

Hey <@U041Z7XSFLK> just to clarify – is this when you’re adding another ingestion task?

And is it safe to presume that `172.31.3.118` is one of your Druid nodes?

Also, are you able to see, on that node itself, the log entries for `index_kafka_nbr_8322bd4a68e5423_pclejmmh` ?  (I _think_ !!! that tasks that start up have logs created but they do not end up in your log store if they fail too early… )

Also I would check that `<http://kafka-int.we-grow.mobi:9094|kafka-int.we-grow.mobi:9094>` is reachable from all the nodes where your Middle Managers are running – and I’d also check there are 3 worker slots available (supervisor + 2 workers)

What is curious is that all your supervisors seem to error when you start up this new one.  Is it safe to assume that this supervisor going to a different datasource?

(It could be a worker capacity thing, I guess – if each one can’t get a slot to do the work)

@ yes Peter. I am adding another ingestion task.

`172.31.3.118`    is another druid node (kubernetes pod)

The logs `index_kafka_nbr_8322bd4a68e5423_pclejmmh`  are disappearing so fast!

yes `<http://kafka-int.we-grow.mobi:9094|kafka-int.we-grow.mobi:9094>`  is reacheable from all druid nodes!

every supervisor is going to a different datasource

OOI when the other tasks start failing, what’s the error that those tasks report?

i also replied here with some thoughts: <https://apachedruidworkspace.slack.com/archives/C0309C9L90D/p1663028734437029?thread_ts=1662982204.176429&amp;cid=C0309C9L90D>

it is better to put all your stuff in a single slack thread so we can coalesce the conversation :slightly_smiling_face: