[
https://issues.apache.org/jira/browse/TAJO-1507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hyunsik Choi updated TAJO-1507:
-------------------------------
Description:
Terminology
* QM - query master
* TM - tajo master
The query kill mechanism is as follows:
* Client sends kill command to TM.
* TM forwards the kill command to QM.
* QM disseminates the kill command to all workers.
* Corresponding workers kill tasks and response KILLED to QM.
BTW, Some workers cannot response KILLED message to QM due to its node failure,
temporary network problem, or worker restart. In this case, TM cannot retrieve
allocated resources even though the workers become normal.
was:
Terminology
* QM - query master
* TM - tajo master
The query kill mechanism is as follows:
* Client sends kill command to TM.
* TM forwards the kill command to QM.
* QM disseminates the kill command to all workers.
* Corresponding workers kill tasks and response KILLED to QM.
BTW, Some workers cannot response KILLED message to QM due to its node failure,
temporary network problem, or worker restart. In this case, TM cannot retrieve
allocated resources even though the worker turns out to be normal.
> Resource leak when a worker does not response KILLED message
> ------------------------------------------------------------
>
> Key: TAJO-1507
> URL: https://issues.apache.org/jira/browse/TAJO-1507
> Project: Tajo
> Issue Type: Improvement
> Components: resource manager, worker
> Reporter: Hyunsik Choi
> Fix For: 0.11.0
>
>
> Terminology
> * QM - query master
> * TM - tajo master
> The query kill mechanism is as follows:
> * Client sends kill command to TM.
> * TM forwards the kill command to QM.
> * QM disseminates the kill command to all workers.
> * Corresponding workers kill tasks and response KILLED to QM.
> BTW, Some workers cannot response KILLED message to QM due to its node
> failure, temporary network problem, or worker restart. In this case, TM
> cannot retrieve allocated resources even though the workers become normal.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)