Skip to content

Conversation

FrankChen021
Copy link
Member

Description

  1. Print the task id of a job in the log
  2. Add a log before job is created for better diagnosis
  3. Fix ISE message
  4. Fix a wrong property name in doc

This PR has:

  • been self-reviewed.
  • added documentation for new or modified features or behaviors.
  • a release note entry in the PR description.
  • added Javadocs for most classes and all non-trivial methods. Linked related entities via Javadoc links.
  • added or updated version, license, or notice information in licenses.yaml
  • added comments explaining the "why" and the intent of the code wherever would not be obvious for an unfamiliar reader.
  • added unit tests or modified existing tests to cover new code paths, ensuring the threshold for code coverage is met.
  • added integration tests.
  • been tested in a test Druid cluster.

Copy link
Contributor

@kfaraz kfaraz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Minor suggestions.

| `druid.indexer.runner.labels` | `JsonObject` | Additional labels you want to add to peon pod. | `{}` | No |
| `druid.indexer.runner.annotations` | `JsonObject` | Additional annotations you want to add to peon pod. | `{}` | No |
| `druid.indexer.runner.peonMonitors` | `JsonArray` | Overrides `druid.monitoring.monitors`. Use this property if you don't want to inherit monitors from the Overlord. | `[]` | No |
| Property | Possible Values | Description | Default | Required |
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The formatting followed in Druid docs is to avoid unnecessary spaces.
So a table typically looks like this:

|Column 1|Column 2|Column 3|
|--------|--------|--------|
|Value 11|Value 12|Long value 13|
|This is a much longer value 21|v22|v23|

I would advise either reverting the formatting changes here (to keep this patch focused on the code change) or sticking to the above format.

I think in the long term, we should also explore the idea of standard formatting for tables etc in docs. I don't think there is any checkstyle or some kind of lint checker that is currently run as a part of docs CI.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Many markdown editors automatically format tables. It's better to solve the format problem in the doc soon.


if (result == null) {
throw new IllegalStateException("K8s pod for the task [%s] appeared and disappeared. It can happen if the task was canceled");
throw new ISE(StringUtils.format("K8s pod for the task [%s] appeared and disappeared. It can happen if the task was canceled", task.getId()));
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think ISE already takes a format string with args, we need not explicitly use StringUtils.format.

FrankChen021 and others added 4 commits June 10, 2025 18:23
…rg/apache/druid/k8s/overlord/common/KubernetesPeonClient.java

Co-authored-by: Kashif Faraz <[email protected]>
…rg/apache/druid/k8s/overlord/common/KubernetesPeonClient.java

Co-authored-by: Kashif Faraz <[email protected]>
…rg/apache/druid/k8s/overlord/common/KubernetesPeonClient.java

Co-authored-by: Kashif Faraz <[email protected]>
@kfaraz kfaraz merged commit af272b4 into apache:master Jun 11, 2025
137 of 138 checks passed
@capistrant capistrant added this to the 34.0.0 milestone Jul 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants