[
https://issues.apache.org/jira/browse/FLINK-10223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16609933#comment-16609933
]
ASF GitHub Bot commented on FLINK-10223:
----------------------------------------
Aitozi opened a new pull request #6679: [FLINK-10223][LOG]Logging with
resourceId during taskmanager startup
URL: https://github.com/apache/flink/pull/6679
## What is the purpose of the change
Log the resourceId during taskmanager startup to help with find the specific
taskmanager when encountering an exception happened in a certain tm
## Brief change log
- add two minor log
## Verifying this change
verify by running a local cluster
```
Jying@Jying:flink-1.7-SNAPSHOT$ cat
log/flink-Jying-taskexecutor-0-Jying-Pro-MacBook.local.log | grep "Starting
taskManager"
2018-09-11 07:55:29,457 INFO
org.apache.flink.runtime.taskexecutor.TaskManagerRunner - Starting
taskManager 13d3e0bab7dcae1d979665acb5afaa31
```
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> TaskManagers should log their ResourceID during startup
> -------------------------------------------------------
>
> Key: FLINK-10223
> URL: https://issues.apache.org/jira/browse/FLINK-10223
> Project: Flink
> Issue Type: Improvement
> Components: Distributed Coordination
> Affects Versions: 1.5.3, 1.6.1, 1.7.0
> Reporter: Konstantin Knauf
> Assignee: aitozi
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.6.1, 1.7.0, 1.5.4
>
>
> To debug exceptions like "org.apache.flink.util.FlinkException: The assigned
> slot <SlotId> was removed." in the master container it is often helpful to
> know, which slot was provided by which Taskmanager. The only way to relate
> slots to TaskManagers right now, seems to be to enable DEBUG logging for
> `org.apache.flink.runtime.jobmaster.slotpool.SlotPool`.
> This would be solved, if each Taskmanager would log out their `ResouceID`
> during startup as the `SlotID` mainly consists of the `ResourceID` of the
> providing Taskmanager. For Mesos and YARN the `ResourceID` has an intrinsic
> meaning, but for a stand-alone or containerized setup the `ResourceID` is
> just the a random ID.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
