[ https://issues.apache.org/jira/browse/GOBBLIN-1620?focusedWorklogId=763696&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-763696 ]
ASF GitHub Bot logged work on GOBBLIN-1620: ------------------------------------------- Author: ASF GitHub Bot Created on: 28/Apr/22 16:28 Start Date: 28/Apr/22 16:28 Worklog Time Spent: 10m Work Description: hanghangliu commented on PR #3487: URL: https://github.com/apache/gobblin/pull/3487#issuecomment-1112412749 @sv2000 As we discussed, I removed trimContainerSize logic, and completely removed the buggy config: private final int minContainers; private final int maxContainers; Issue Time Tracking ------------------- Worklog Id: (was: 763696) Time Spent: 3h 10m (was: 3h) > 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: 3h 10m > 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)