FrankChen021 opened a new pull request, #20833:
URL: https://github.com/apache/druid/pull/20833
### Description
Druid allows a plain space in datasource names (`IdUtils.validateId` only
rejects whitespace other than a space), and most task ids embed the datasource
name, e.g. `index_kafka_<datasource>_...`,
`coordinator-issued_kill_<datasource>_...`. When such a task runs with the
Kubernetes task runner, the peon pod fails before `CliPeon` starts:
```
/peon.sh: 166: cannot create var/tmp/coordinator-issued_kill_my
ds_..._2026-11-04T05:09:41.064Z/task.json: Directory nonexistent
```
and the Overlord marks the task `FAILED` with `Peon did not report status
successfully.`.
#### Impact scope
Only the Kubernetes task runner (`druid-kubernetes-overlord-extensions`) is
affected. For a datasource whose name contains a space, all streaming
ingestion, native batch, compaction and kill tasks fail to start. MSQ tasks
(`query-<uuid>`) are not affected.
#### Release note
Fixed Kubernetes peon tasks failing to start with "Peon did not report
status successfully." when the task id contains a space, e.g. for datasources
whose name contains a space.
<hr>
##### Key changed/added classes in this PR
* `distribution/docker/peon.sh`
<hr>
This PR has:
- [x] been self-reviewed.
- [x] a release note entry in the PR description.
- [x] been tested in a test Druid cluster.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
