You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# Before running ingestion task
nc: connect to druid-data-0.data-pods (10.244.3.14) port 8100 (tcp) failed: Connection refused
nc: connect to druid-data-0.data-pods (10.244.3.14) port 8100 (tcp) failed: Connection refused
nc: connect to druid-data-0.data-pods (10.244.3.14) port 8100 (tcp) failed: Connection refused
nc: connect to druid-data-0.data-pods (10.244.3.14) port 8100 (tcp) failed: Connection refused
# During the task
Connection to druid-data-0.data-pods (10.244.3.14) 8100 port [tcp/*] succeeded!
Connection to druid-data-0.data-pods (10.244.3.14) 8100 port [tcp/*] succeeded!
Connection to druid-data-0.data-pods (10.244.3.14) 8100 port [tcp/*] succeeded!
# After the task
nc: connect to druid-data-0.data-pods (10.244.3.14) port 8100 (tcp) failed: Connection refused
nc: connect to druid-data-0.data-pods (10.244.3.14) port 8100 (tcp) failed: Connection refused
nc: connect to druid-data-0.data-pods (10.244.3.14) port 8100 (tcp) failed: Connection refused
To be honest I'm confused as to why Coordinator is even trying to reach the Peon for task logs. Given that Peons are ephemeral and exit once the task is done, it would make much more sense to get those logs from the Middle Manager whose job is to manage the Peons.
What am I missing?
The text was updated successfully, but these errors were encountered:
I have a Druid cluster running on Kubernetes. I have allowed port 8100 through the data-service pod and service.
When running an ingestion task I see this error.
However the task runs and ingests the data.
Affected Version
29.0.1
Description
In the coordinator logs I see this error. Which implies that it cannot reach data service on port 8100.
The port is indeed open and the Peon service is listening on it during task execution which I've verifed by running this:
Which prints:
To be honest I'm confused as to why Coordinator is even trying to reach the Peon for task logs. Given that Peons are ephemeral and exit once the task is done, it would make much more sense to get those logs from the Middle Manager whose job is to manage the Peons.
What am I missing?
The text was updated successfully, but these errors were encountered: