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 2021/05/17 12:18:34 UTC

[GitHub] [dolphinscheduler] geosmart edited a comment on issue #5186: [Bug][MASTER] DS kill all yarn apps

geosmart edited a comment on issue #5186:
URL: https://github.com/apache/dolphinscheduler/issues/5186#issuecomment-842277139


   > We need to change the storage method of appid, it is best to store it in DB, If at the time of kill (usually when fault tolerance is needed), first call the API to determine the final execution result of the yarn task, whether it will be better.
   
   when worker shutdown, it's yarn task will failover, and the master get the yarn applicationId by the task log file ,and the task log is come from a logServer witch run in the shutdown worker...
   so you just can't failover ,if your worker is down  
   
   so we realy need to store the applicationId to do failover.
   
   does we already have any this yarn application  failover pr?


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