Savonitar opened a new pull request, #28857:
URL: https://github.com/apache/flink/pull/28857
<!--
*Thank you very much for contributing to Apache Flink - we are happy that
you want to help us improve Flink. To help the community review your
contribution in the best possible way, please go through the checklist below,
which will get the contribution into a shape in which it can be best reviewed.*
*Please understand that we do not do this to make contributions to Flink a
hassle. In order to uphold a high standard of quality for code contributions,
while at the same time managing a large number of contributions, we need
contributors to prepare the contributions well, and give reviewers enough
contextual information for the review. Please also understand that
contributions that do not follow this guide will take longer to review and thus
typically be picked up with lower priority by the community.*
## Contribution Checklist
- Make sure that the pull request corresponds to a [JIRA
issue](https://issues.apache.org/jira/projects/FLINK/issues). Exceptions are
made for typos in JavaDoc or documentation files, which need no JIRA issue.
- Name the pull request in the form "[FLINK-XXXX] [component] Title of the
pull request", where *FLINK-XXXX* should be replaced by the actual issue
number. Skip *component* if you are unsure about which is the best component.
Typo fixes that have no associated JIRA issue should be named following
this pattern: `[hotfix] [docs] Fix typo in event time introduction` or
`[hotfix] [javadocs] Expand JavaDoc for PuncuatedWatermarkGenerator`.
- Fill out the template below to describe the changes contributed by the
pull request. That will give reviewers the context they need to do the review.
- Make sure that the change passes the automated tests, i.e., `mvn clean
verify` passes. You can set up Azure Pipelines CI to do that following [this
guide](https://cwiki.apache.org/confluence/display/FLINK/Azure+Pipelines#AzurePipelines-Tutorial:SettingupAzurePipelinesforaforkoftheFlinkrepository).
- Each pull request should address only one issue, not mix up code from
multiple issues.
- Each commit in the pull request has a meaningful commit message
(including the JIRA id)
- Once all items of the checklist are addressed, remove the above text and
this checklist, leaving only the filled out template below.
**(The sections below can be removed for hotfixes of typos)**
-->
## What is the purpose of the change
On a session / multi-tenant TaskManager, source data-plane and coordinator
threads carry no job identity, so their logs and thread dumps cannot be
attributed to a job (source operator names collide across jobs). Building on
the `JobInfo` API from FLINK-39776, this PR closes three gaps:
1. **Split fetcher threads** (`SplitFetcherManager`): the fetcher pool did
not inherit the task thread's SLF4J MDC, so every connector `SplitReader`
logged with an empty `flink-job-id`, and the "Source Data Fetcher for ..."
thread name carried no job identity.
2. **Source coordinator worker executor** (`SourceCoordinatorContext`):
`callAsync` work (e.g. periodic file-split scans) still logged without
`flink-job-id`.
3. **Coordinator thread name** (`SourceCoordinatorProvider`):
`SourceCoordinator-<operatorName>` is identical for two jobs using the same
source operator name. The thread-name suffix (truncated job name + full hex job
id) deliberately matches the `flink-job-id` MDC value, so thread dumps
correlate with log output.
## Brief change log
- `MdcUtils`: new `jobThreadNameSuffix(JobInfo)` helper (job name capped at
32 chars, the length of the hex `JobID` that follows it).
- `SplitFetcherManager` / `SingleThreadFetcherManager`: new constructor
overload with a trailing `@Nullable JobInfo`, when provided, the thread factory
seeds the job id into each pool thread's MDC once and appends the job suffix to
the thread name. All existing constructors delegate with `null` and **_keep
their exact previous behavior._**
- `SourceCoordinatorContext`: worker executor wrapped with
`MdcUtils.scopeToJob`.
- `SourceCoordinatorProvider`: job suffix appended to the coordinator thread
name (the derived `-worker` pool inherits it).
## Verifying this change
This change added tests:
- `MdcUtilsTest`: suffix format, exact truncation boundary (at cap / cap +
1), empty and null job names.
- `SplitFetcherManagerTest`: on a real fetcher thread, the MDC carries the
job id and the thread name carries the exact suffix; the no-`JobInfo`
constructors preserve the historical thread name and empty MDC.
- `SourceCoordinatorContextTest`: `callAsync` callables run with the job id
in the MDC.
- `SourceCoordinatorProviderTest`: the lazily created coordinator thread's
name contains the job name and id.
## Does this pull request potentially affect one of the following parts:
- Dependencies (does it add or upgrade a dependency): (no)
- The public API, i.e., is any changed class annotated with
`@Public(Evolving)`: (yes / no)
- The serializers: (no)
- The runtime per-record code paths (performance sensitive): (no)
- Anything that affects deployment or recovery: JobManager (and its
components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (no)
- The S3 file system connector: (no)
## Documentation
- Does this pull request introduce a new feature? (no)
- If yes, how is the feature documented? (not applicable)
---
##### Was generative AI tooling used to co-author this PR?
<!--
If generative AI tooling has been used in the process of authoring this PR,
please
change the checkbox below to `[X]` and replace the placeholder in the
"Generated-by"
line with the tool name and version. Otherwise remove the "Generated-by"
line.
See the ASF Generative Tooling Guidance for details:
https://www.apache.org/legal/generative-tooling.html
You are responsible for the quality and correctness of every change in this
PR
regardless of the tooling used. Low-effort AI-generated PRs will be closed.
See
AGENTS.md for the full guidance.
-->
- [ ] Yes (please specify the tool below)
Generated-by: Claude Opus 4.8 (1M context) <[email protected]>
--
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]
