[
https://issues.apache.org/jira/browse/GOBBLIN-1823?focusedWorklogId=862030&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-862030
]
ASF GitHub Bot logged work on GOBBLIN-1823:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 22/May/23 18:58
Start Date: 22/May/23 18:58
Worklog Time Spent: 10m
Work Description: ZihanLi58 merged PR #3692:
URL: https://github.com/apache/gobblin/pull/3692
Issue Time Tracking
-------------------
Worklog Id: (was: 862030)
Time Spent: 1h (was: 50m)
> Improving Container Calculation and Allocation Methodology
> ----------------------------------------------------------
>
> Key: GOBBLIN-1823
> URL: https://issues.apache.org/jira/browse/GOBBLIN-1823
> Project: Apache Gobblin
> Issue Type: Improvement
> Reporter: Zihan Li
> Priority: Major
> Time Spent: 1h
> Remaining Estimate: 0h
>
> When Yarn allocates "ghost containers" without calling the
> onContainerAllocated() method and when the container is eventually released,
> onContainersCompleted() is called, container numbers mismatches can occur.
> In the onContainerAllocated() method, we add the container to the
> containerMap using the container ID as the key, and increase the count for
> the specific tag.
> In the onContainersCompleted() method, we remove the container from the
> containerMap and decrease the count. However, in some cases, we find that the
> containerMap does not contain the ID, and we ignore this while still
> decreasing the number of the allocated tag. We do this because sometimes
> onContainersCompleted() is called before onContainerAllocated() for the same
> container.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
