[
https://issues.apache.org/jira/browse/GOBBLIN-1781?focusedWorklogId=845258&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-845258
]
ASF GitHub Bot logged work on GOBBLIN-1781:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 14/Feb/23 02:02
Start Date: 14/Feb/23 02:02
Worklog Time Spent: 10m
Work Description: Will-Lo merged PR #3638:
URL: https://github.com/apache/gobblin/pull/3638
Issue Time Tracking
-------------------
Worklog Id: (was: 845258)
Time Spent: 1h 40m (was: 1.5h)
> Helix offline instance purging is not thread safe in the yarn service
> ---------------------------------------------------------------------
>
> Key: GOBBLIN-1781
> URL: https://issues.apache.org/jira/browse/GOBBLIN-1781
> Project: Apache Gobblin
> Issue Type: Bug
> Reporter: Andy Jiang
> Priority: Major
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> Helix instances are purged during startup of the yarn service. This operation
> must be done without new helix instances being added or removed (i.e. the API
> call is not thread safe).
>
> The current implementation blocks the yarn service from allocating initial
> containers while the helix instance purging is enabled, but it does not
> prevent other external services from requesting containers through its public
> methods.
> These 2 services start up concurrently, and it's possible that the
> AutoScalingYarnManager starts up before the Yarn Service is completely
> finished purging. This means leads to the AutoScalingYarnManager to
> requestContainers while the instances are still purging.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
