ruanwenjun commented on issue #11262: URL: https://github.com/apache/dolphinscheduler/issues/11262#issuecomment-1203709389
> @ruanwenjun Yeh, maybe a practicable solution, we can simply talk about it. > > Before submitting a yarn job, the client apply the application context from RM first, and get appId which will be then written into NM's environment variable. We can use java agent to read it before executing yarn job's JAR file, also, can take taskInstanceId as input of agent program. However, where to store this mapping relationship need to be further considered. > > Please let me know if you have any good suggestions! In fact, there is already a issue talk about use agent to collect the appId, but I think it isn't a good way 😢 -- 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]
