[
https://issues.apache.org/jira/browse/GOBBLIN-2189?focusedWorklogId=957758&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-957758
]
ASF GitHub Bot logged work on GOBBLIN-2189:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 19/Feb/25 14:32
Start Date: 19/Feb/25 14:32
Worklog Time Spent: 10m
Work Description: Blazer-007 commented on code in PR #4092:
URL: https://github.com/apache/gobblin/pull/4092#discussion_r1961792962
##########
gobblin-temporal/src/main/java/org/apache/gobblin/temporal/yarn/AbstractDynamicScalingYarnServiceManager.java:
##########
@@ -110,9 +110,13 @@ public void run() {
List<ScalingDirective> scalingDirectives =
scalingDirectiveSource.getScalingDirectives();
if (CollectionUtils.isNotEmpty(scalingDirectives)) {
dynamicScalingYarnService.reviseWorkforcePlanAndRequestNewContainers(scalingDirectives);
+ } else {
+ dynamicScalingYarnService.calcDeltasAndRequestContainers();
}
} catch (FileNotFoundException fnfe) {
- log.warn("Failed to get scaling directives - " + fnfe.getMessage());
// important message, but no need for a stack trace
+ log.debug("Failed to get scaling directives - " + fnfe.getMessage());
// important message, but no need for a stack trace
Review Comment:
Yes it will be useful for debugging but currently it is getting printed too
many times as background thread is running at an interval of 1 minute that's
why changed to debug log level.
Let me know if we need it to change it back to warn
Issue Time Tracking
-------------------
Worklog Id: (was: 957758)
Time Spent: 4h 10m (was: 4h)
> Implement ContainerCompletion callback in DynamicScalingYarnService
> -------------------------------------------------------------------
>
> Key: GOBBLIN-2189
> URL: https://issues.apache.org/jira/browse/GOBBLIN-2189
> Project: Apache Gobblin
> Issue Type: Improvement
> Components: gobblin-core
> Reporter: Vivek Rai
> Assignee: Abhishek Tiwari
> Priority: Major
> Time Spent: 4h 10m
> Remaining Estimate: 0h
>
> DynamicScalingYarnService currently doesn't handle scaling down containers
> and neither does anything if container is killed abruptly or goes OOM. So to
> handle this scenario containerCompletion callback should be implemented to
> launch the replacement containers and also scaling down handling should be
> done.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
