[
https://issues.apache.org/jira/browse/GOBBLIN-1620?focusedWorklogId=763693&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-763693
]
ASF GitHub Bot logged work on GOBBLIN-1620:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 28/Apr/22 16:25
Start Date: 28/Apr/22 16:25
Worklog Time Spent: 10m
Work Description: hanghangliu commented on code in PR #3487:
URL: https://github.com/apache/gobblin/pull/3487#discussion_r861090379
##########
gobblin-yarn/src/main/java/org/apache/gobblin/yarn/YarnService.java:
##########
@@ -479,32 +495,48 @@ public synchronized void
requestTargetNumberOfContainers(int numTargetContainers
this.eventBus.post(new ContainerReleaseRequest(containersToRelease));
}
-
+ this.yarnContainerRequest = yarnContainerRequestBundle;
Review Comment:
It is being used by the private class AMRMClientCallbackHandler for
determining the helix tag that need to be assigned to the allocated container
Issue Time Tracking
-------------------
Worklog Id: (was: 763693)
Time Spent: 2h 50m (was: 2h 40m)
> Make yarn container allocation group by helix tag
> -------------------------------------------------
>
> Key: GOBBLIN-1620
> URL: https://issues.apache.org/jira/browse/GOBBLIN-1620
> Project: Apache Gobblin
> Issue Type: New Feature
> Components: gobblin-cluster
> Reporter: Hanghang Liu
> Assignee: Hung Tran
> Priority: Major
> Time Spent: 2h 50m
> Remaining Estimate: 0h
>
> This change enable Helix instances use the specific tag defined(if exists) in
> their Job/Workflow. This makes the Helix cluster management easier and more
> strait forward, as each job's instances can carry unique Helix tag.
> In this case, for each Gobblin job run, helix tasks within this job will
> be assigned to containers with desired helix tag and resource.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
