You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@gobblin.apache.org by "Hanghang Liu (Jira)" <ji...@apache.org> on 2022/06/17 18:26:00 UTC
[jira] [Updated] (GOBBLIN-1665) Fix bug when decreasing requestedContainerCountMap
[ https://issues.apache.org/jira/browse/GOBBLIN-1665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hanghang Liu updated GOBBLIN-1665:
----------------------------------
Description:
The place we try to update(especially decrease) the requestedContainerCountMap is not correct now. Inside
requestTargetNumberOfContainers method, we should only increase the map if requestContainer is called. The place we should decrease the count in the map should be the place we shrink the container count, which means we're purposely releasing containers and won't spawn replacement.
was:
The place we try to decrease the requestedContainerCountMap is not correct now. Inside
requestTargetNumberOfContainers method we should only increase the map if requestContainer is called. The only place we should decrease the count in the map should be handleContainerCompletion, while ContainerExitStatus is ABORTED, meaning we're purposely releasing a container.
> Fix bug when decreasing requestedContainerCountMap
> --------------------------------------------------
>
> Key: GOBBLIN-1665
> URL: https://issues.apache.org/jira/browse/GOBBLIN-1665
> Project: Apache Gobblin
> Issue Type: Bug
> Components: gobblin-yarn
> Reporter: Hanghang Liu
> Assignee: Abhishek Tiwari
> Priority: Major
>
> The place we try to update(especially decrease) the requestedContainerCountMap is not correct now. Inside
> requestTargetNumberOfContainers method, we should only increase the map if requestContainer is called. The place we should decrease the count in the map should be the place we shrink the container count, which means we're purposely releasing containers and won't spawn replacement.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)