[ 
https://issues.apache.org/jira/browse/YARN-9384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Zhang updated YARN-9384:
------------------------
    Description: 
Today KillApplication request from user client only goes to home cluster. As a 
result the containers in secondary clusters continue processing for 10~15 
minutes (UAM heartbeat timeout).

This is not an favorable user experience especially when user has a streaming 
job and sometime needs to restart it (like updating config or resources). In 
this case, containers created by new job and old job can run at the same time.

  was:
Today KillApplication request from user client only goes to home cluster. As a 
result the containers in secondary clusters continue working for 10~15 minutes 
(UAM heartbeat timeout).

This is not an favorable user experience especially when user has a streaming 
job and sometime needs to restart it. In this case, containers created by new 
job and old job can run at the same time.


> FederationInterceptorREST should broadcast KillApplication to all sub clusters
> ------------------------------------------------------------------------------
>
>                 Key: YARN-9384
>                 URL: https://issues.apache.org/jira/browse/YARN-9384
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: federation
>            Reporter: Zhang
>            Priority: Major
>              Labels: federation
>         Attachments: YARN-9384.patch
>
>
> Today KillApplication request from user client only goes to home cluster. As 
> a result the containers in secondary clusters continue processing for 10~15 
> minutes (UAM heartbeat timeout).
> This is not an favorable user experience especially when user has a streaming 
> job and sometime needs to restart it (like updating config or resources). In 
> this case, containers created by new job and old job can run at the same time.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to