You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@dolphinscheduler.apache.org by GitBox <gi...@apache.org> on 2020/07/14 03:04:35 UTC

[GitHub] [incubator-dolphinscheduler] qiaozhanwei commented on pull request #2363: add stop spark task instance feature

qiaozhanwei commented on pull request #2363:
URL: https://github.com/apache/incubator-dolphinscheduler/pull/2363#issuecomment-657938757


   > > -1
   > > 1, api cannot depend on server module
   > > 2. DS has a kill operation, why should you develop a kill operation yourself?
   > 
   > emm, the first one, api dependon server module surely not reasonable, I agree;but the second one, DS current kill operation will not work when yarn is in other machine which diffrent from the work running machine, or, some scenes, I just want kill a task, not the whole workflow, so I think a kill operation in task level will better. Maybe the demand is too absurd, there are few such needs in practice... I just show my a little idea.
   
   yarn-client and yarn-cluster different is driver log print . appId we can collected and use sudo kill -9 Pid and yarn application -kill appId
   
   


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

For queries about this service, please contact Infrastructure at:
users@infra.apache.org