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/22 22:11:00 UTC

[jira] [Closed] (GOBBLIN-1661) Make Yarn container and helix instance allocation group by tag

     [ https://issues.apache.org/jira/browse/GOBBLIN-1661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hanghang Liu closed GOBBLIN-1661.
---------------------------------
    Resolution: Fixed

> Make Yarn container and helix instance allocation group by tag
> --------------------------------------------------------------
>
>                 Key: GOBBLIN-1661
>                 URL: https://issues.apache.org/jira/browse/GOBBLIN-1661
>             Project: Apache Gobblin
>          Issue Type: New Feature
>          Components: gobblin-helix, gobblin-yarn
>            Reporter: Hanghang Liu
>            Assignee: Abhishek Tiwari
>            Priority: Major
>
> 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 can make within one Gobblin job run, multiple resource config can be set for different topics, instead of the need of creating new Helix cluster for different Gobblin job run setting.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)