[
https://issues.apache.org/jira/browse/TAJO-1508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14652937#comment-14652937
]
Jinho Kim commented on TAJO-1508:
---------------------------------
This issue was fixed by TAJO-1599. Please close this
The ResourceTracker can update resource capacities as following:
* First join or rejoin(restart)
* Startup the master node after startup the worker node.
> ResourceTracker does not update workers' resource capacities after the first
> join
> ---------------------------------------------------------------------------------
>
> Key: TAJO-1508
> URL: https://issues.apache.org/jira/browse/TAJO-1508
> Project: Tajo
> Issue Type: Improvement
> Components: Resource Manager, Worker
> Reporter: Hyunsik Choi
> Assignee: Jihun Kang
> Fix For: 0.11.0
>
>
> h3. Background
> Resource Tracker (RT) registers a worker with its connection info and
> resource capacity into RMContext when the worker sends the first heartbeat to
> RT.
> h3. Problem
> * All heartbeats that each worker sends to RT always include the resource
> capacity. It is not necessary and inefficient in terms of network costs.
> * After the first heartbeat, RT does not update the resource capacity of the
> worker even though the resource capacity of the same worker is changed. This
> case is unusual, but it is possible. For example, some workers can rejoin to
> the Tajo cluster with modified resource capacities. But, RT will still keep
> previous resource capacity.
> h3. Solution
> * We should change resource capacity of heartbeat to optional fields.
> * Only the first heartbeat of each worker includes the resource capacity of
> the worker.
> * When a resource capacity field of heartbeat is set, RT updates the resource
> capacity for the worker.
> This solution will reduce the size of heartbeat message and will enable RT to
> update changed resource capacity of workers.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
