zhuzhurk opened a new pull request #7308: [FLINK-11165] Refine the task 
deploying log for easier finding of tas…
URL: https://github.com/apache/flink/pull/7308
 
 
   …k locations
   
   ## What is the purpose of the change
   
   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:
   "Deploying Flat Map (31/40) (attempt #0) to z05c19399"
   
   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 full task manager location representation in 
the deploying log to support quick locating tasks. The task manager location 
contains resourceId. The resourceId is the containerId when job runs in 
yarn/mesos, or a unique AbstractID in standalone mode which can be easily 
identified at Flink web UI. 
   
   ## Brief change log
   
   Changed the task deploying log to print the full task manager location, 
including the resourceID
   
   ## Verifying this change
   
     -*This change is a trivial rework / code cleanup without any test 
coverage.*
     - *Manually verified by execution IT cases can check the deploying log*
   
   ## 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)`: (no)
     - The serializers: (no)
     - The runtime per-record code paths (performance sensitive): (no)
     - Anything that affects deployment or recovery: JobManager (and its 
components), Checkpointing, Yarn/Mesos, 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 documented)
   

----------------------------------------------------------------
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


With regards,
Apache Git Services

Reply via email to