[
https://issues.apache.org/jira/browse/AURORA-370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Khutornenko updated AURORA-370:
-------------------------------------
Description:
The killTasks RPC is currently waiting for a task to get killed actively
blocking the client thread. With the killTaskMaxBackoff set at 1 minute the
delayed killTasks call effectively destroys any multiprocessing attempts on the
client.
Move the kill wait to the client potentially reusing the existing JobMonitor.
was:
The killTasks RPC is currently waiting for a task to get killed actively
blocking the client thread. With the killTaskMaxBackoff set at 1 minute the
delayed killTasks call effectively destroys any multiprocessing attempts on the
client.
Move the kill wait to the client potentially reusing the existing JobMonitor
and WAIT_UNTIL_OPTION.
> The killTasks RPC should not wait until tasks are killed
> --------------------------------------------------------
>
> Key: AURORA-370
> URL: https://issues.apache.org/jira/browse/AURORA-370
> Project: Aurora
> Issue Type: Story
> Components: Client, Scheduler
> Reporter: Maxim Khutornenko
> Assignee: Maxim Khutornenko
>
> The killTasks RPC is currently waiting for a task to get killed actively
> blocking the client thread. With the killTaskMaxBackoff set at 1 minute the
> delayed killTasks call effectively destroys any multiprocessing attempts on
> the client.
> Move the kill wait to the client potentially reusing the existing JobMonitor.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
