You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Roman Khachatryan (Jira)" <ji...@apache.org> on 2026/07/31 14:20:00 UTC

[jira] [Assigned] (FLINK-40270) Make source fetcher and coordinator threads job-attributable (MDC + thread names)

     [ https://issues.apache.org/jira/browse/FLINK-40270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Roman Khachatryan reassigned FLINK-40270:
-----------------------------------------

    Assignee: Aleksandr Savonin

> Make source fetcher and coordinator threads job-attributable (MDC + thread names)
> ---------------------------------------------------------------------------------
>
>                 Key: FLINK-40270
>                 URL: https://issues.apache.org/jira/browse/FLINK-40270
>             Project: Flink
>          Issue Type: Sub-task
>          Components: API / Core, Connectors / Common, Runtime / Coordination
>            Reporter: Aleksandr Savonin
>            Assignee: Aleksandr Savonin
>            Priority: Major
>
> On a session / multi-tenant TaskManager, source threads are not attributable to a job:
>  # SplitFetcherManager's fetcher threads don't inherit the task thread's SLF4J MDC, so every connector SplitReader logs with an empty flink-job-id. the "Source Data Fetcher for ..." thread name has no job identity either.
>  # SourceCoordinatorContext's worker executor is not job-scoped, so callAsync work such as periodic file-split scans logs without flink-job-id.
>  # The "SourceCoordinator-" thread name is identical for two jobs using the same source operator name.
> Building on FLINK-39776 (JobInfo on source contexts).



--
This message was sent by Atlassian Jira
(v8.20.10#820010)