[jira] [Resolved] (TEZ-4689) Introduce Node abstraction for DAGAppMaster instead of separate NodeManager-related fields

["László Bodor (Jira)" <ji...@apache.org>]

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

László Bodor resolved TEZ-4689.
-------------------------------
    Resolution: Fixed

> Introduce Node abstraction for DAGAppMaster instead of separate NodeManager-related fields
> ------------------------------------------------------------------------------------------
>
>                 Key: TEZ-4689
>                 URL: https://issues.apache.org/jira/browse/TEZ-4689
>             Project: Apache Tez
>          Issue Type: Sub-task
>            Reporter: László Bodor
>            Assignee: Raghav Aggarwal
>            Priority: Major
>             Fix For: 1.0.0
>
>          Time Spent: 7h
>  Remaining Estimate: 0h
>
> In DAGAppMaster.main I can see:
> {code}
>       String nodeHostString = System.getenv(ApplicationConstants.Environment.NM_HOST.name());
>       String nodePortString = System.getenv(ApplicationConstants.Environment.NM_PORT.name());
>       String nodeHttpPortString = System.getenv(ApplicationConstants.Environment.NM_HTTP_PORT.name());
> {code}
> this is problematic in different ways:
> 1. we're currently decoupling Tez from Yarn, we should abstract these and lazy-resolve them when they are really needed
> 2. they pollute the DAGAppMaster constructor: we should use a single `NodeContext`, which maybe can implemented by `YarnNameNodeContext` while running on Yarn



--
This message was sent by Atlassian Jira
(v8.20.10#820010)