You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@amaterasu.apache.org by "Eyal Ben Ivri (JIRA)" <ji...@apache.org> on 2018/04/21 08:51:00 UTC
[jira] [Updated] (AMATERASU-22) Improve the way yarn containers are
allocated to consider specific task requirments
[ https://issues.apache.org/jira/browse/AMATERASU-22?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eyal Ben Ivri updated AMATERASU-22:
-----------------------------------
Description:
Currently, YARN containers are created without consideration for specific requirements of a task, just the job configuration.
As a pipeline developer, I would like to be able to override the specifications (v-cores or memory) of a specific task inside a flow.
was:
Currently, YARN containers are created without consideration for specific requirements of a task, just the job configuration.
As a Flow developer, i would like to be able to override the specifications (vcores or memory) of a specific task inside a flow.
> Improve the way yarn containers are allocated to consider specific task requirments
> -----------------------------------------------------------------------------------
>
> Key: AMATERASU-22
> URL: https://issues.apache.org/jira/browse/AMATERASU-22
> Project: AMATERASU
> Issue Type: Improvement
> Reporter: Eyal Ben Ivri
> Assignee: Eyal Ben Ivri
> Priority: Major
> Fix For: 0.2.1-incubating
>
>
> Currently, YARN containers are created without consideration for specific requirements of a task, just the job configuration.
> As a pipeline developer, I would like to be able to override the specifications (v-cores or memory) of a specific task inside a flow.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)