[
https://issues.apache.org/jira/browse/GOBBLIN-1091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sudarshan Vasudevan resolved GOBBLIN-1091.
------------------------------------------
Resolution: Fixed
> Pass Yarn application id as part of AppMaster and YarnTaskRunner's start up
> command
> -----------------------------------------------------------------------------------
>
> Key: GOBBLIN-1091
> URL: https://issues.apache.org/jira/browse/GOBBLIN-1091
> Project: Apache Gobblin
> Issue Type: Improvement
> Components: gobblin-yarn
> Affects Versions: 0.15.0
> Reporter: Sudarshan Vasudevan
> Assignee: Abhishek Tiwari
> Priority: Major
> Fix For: 0.15.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Currently, the application id is retrieved from the container id in Gobblin
> Yarn applications. This makes it hard to isolate the source of
> misconfigurations in the application work directory (i.e. Yarn vs Helix vs
> Gobblin), which is generated dynamically using Yarn application name and Yarn
> application id. Having the Yarn application id generated in one place (i.e.
> GobblinYarnAppLauncher) and passed to all participants in the Yarn
> application ensures a more explainable and debuggable behavior in how
> application working directories are set.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
