You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@samza.apache.org by "Yi Pan (Data Infrastructure) (JIRA)" <ji...@apache.org> on 2017/03/19 07:18:42 UTC

[jira] [Assigned] (SAMZA-1138) Yarn capability check is broken

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

Yi Pan (Data Infrastructure) reassigned SAMZA-1138:
---------------------------------------------------

    Assignee: Maksim Logvinenko

> Yarn capability check is broken
> -------------------------------
>
>                 Key: SAMZA-1138
>                 URL: https://issues.apache.org/jira/browse/SAMZA-1138
>             Project: Samza
>          Issue Type: Bug
>            Reporter: Maksim Logvinenko
>            Assignee: Maksim Logvinenko
>
> After migration from yarn.container.* properties to cluster-manager.container.* properties we have to use either of them and ClusterManagerConfig provides backward compatibility for these properties. But in YarnClusterResourceManager only old properties are used (from YarnConfig), hence if job config migrated to new cluster-manager.* properties names then check will be evaluated against default values, not against actual values.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)