Radeity commented on issue #11262: URL: https://github.com/apache/dolphinscheduler/issues/11262#issuecomment-1255877159
Hi, Rick First, thanks for your idea! However, i think this way have two problems as follow: 1. Users may create ShellTask and submit not only one yarn job via command lines which is hard to add configuration. 2. Aop way will simply fetch applicationId and write it into appInfo.log file. I think it's maybe more efficiency than query it through unique tag. In fact, I don't get how your idea work? Would you like to explain more about it? Best wishes rickchengx ***@***.***> 于2022年9月23日周五 14:35写道： > Hi, @Radeity <https://github.com/Radeity> @ruanwenjun > <https://github.com/ruanwenjun> > > I agree that the current way of getting the yarn application id from the > log is not elegant. > Just for discussion, there is another way to get yarn application id as > below: > > We can put some *unique tags* on tasks submitted from DS to yarn. E.g., > for spark tasks, we can add the configuration --conf spark.yarn.tags > some_unique_tag. > After the task is submitted, DS can query the corresponding yarn > application id (or other info) through this unique tag. > > What do you think? Any comments or discussions are welcome. > > — > Reply to this email directly, view it on GitHub > <https://github.com/apache/dolphinscheduler/issues/11262#issuecomment-1255845285>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AKY23YTHFBEZSS7FEWPLJ4TV7VFTTANCNFSM55KW2JOQ> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> > -- 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]
