[ 
https://issues.apache.org/jira/browse/GOBBLIN-2050?focusedWorklogId=915582&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-915582
 ]

ASF GitHub Bot logged work on GOBBLIN-2050:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 19/Apr/24 16:49
            Start Date: 19/Apr/24 16:49
    Worklog Time Spent: 10m 
      Work Description: Will-Lo opened a new pull request, #3931:
URL: https://github.com/apache/gobblin/pull/3931

   …ctories to allow easy cleanup after job completion
   
   Dear Gobblin maintainers,
   
   Please accept this PR. I understand that it will not be reviewed until I 
have checked off all the steps below!
   
   
   ### JIRA
   - [ ] My PR addresses the following [Gobblin 
JIRA](https://issues.apache.org/jira/browse/GOBBLIN/) issues and references 
them in the PR title. For example, "[GOBBLIN-XXX] My Gobblin PR"
       - https://issues.apache.org/jira/browse/GOBBLIN-2050
   
   
   ### Description
   - [ ] Here are some details about my PR, including screenshots (if 
applicable):
   Gobblin Yarn Application Launcher has some issues where directories used for 
the job can persist after the job ends. It also creates a number of temporary 
files which can grow out of control.
   
   This PR creates a new instance of a file system for cleaning up as the 
previous filesystem instance gets closed by the Yarn application and the cache 
becomes problematic with mount table FS.
   It also allows a user to define `gobblin.cluster.absolute.workDir` for the 
exact path their cluster temp files and jars are stored, and 
`gobblin.yarn.token.file.path` to determine where to store their yarn security 
token.
   
   ### Tests
   - [ ] My PR adds the following unit tests __OR__ does not need testing for 
this extremely good reason:
   
   
   ### Commits
   - [ ] My commits all reference JIRA issues in their subject lines, and I 
have squashed multiple commits if they address the same issue. In addition, my 
commits follow the guidelines from "[How to write a good git commit 
message](http://chris.beams.io/posts/git-commit/)":
       1. Subject is separated from body by a blank line
       2. Subject is limited to 50 characters
       3. Subject does not end with a period
       4. Subject uses the imperative mood ("add", not "adding")
       5. Body wraps at 72 characters
       6. Body explains "what" and "why", not "how"
   
   




Issue Time Tracking
-------------------

            Worklog Id:     (was: 915582)
    Remaining Estimate: 0h
            Time Spent: 10m

> Allow configurable token file paths and cluster work directories to allow for 
> easy cleanup after yarn app closes
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: GOBBLIN-2050
>                 URL: https://issues.apache.org/jira/browse/GOBBLIN-2050
>             Project: Apache Gobblin
>          Issue Type: Improvement
>            Reporter: William Lo
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Gobblin Yarn Application Launcher has some issues where directories used for 
> the job can persist after the job ends. It also creates a number of temporary 
> files which can grow out of control.
> We want to be able to:
> 1. Clean up directories effectively
> 2. Use explicit paths to allow for consolidation of temp files to be under 
> the same folder for token renewal and cluster work files.



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

Reply via email to