Zhu Zhu created FLINK-11165:
-------------------------------
Summary: Refine the deploying log for easier finding of task
locations
Key: FLINK-11165
URL: https://issues.apache.org/jira/browse/FLINK-11165
Project: Flink
Issue Type: Improvement
Components: Distributed Coordination
Affects Versions: 1.7.0
Reporter: Zhu Zhu
Assignee: Zhu Zhu
Currently there is not a straight forward way to find in which TM a task
locates in, especially when the task has failed.
We can find on which machine the task locates in by checking the JM log, sample
as below:
{color:#707070}_"Deploying Flat Map (31/40) (attempt #0) to z05c19399"_{color}
But there can be multiple TMs on the machine and we need to check them one by
one. *So I'd suggest we add the TM resourceId in the deploying log to support
quick locating tasks.* The TM resourceId is containerId when job runs in
yarn/mesos, and a unique AbstractID in standalone mode which can be easily
matched at Flink web UI.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
