[ 
https://issues.apache.org/jira/browse/YARN-10313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18044565#comment-18044565
 ] 

ASF GitHub Bot commented on YARN-10313:
---------------------------------------

github-actions[bot] commented on PR #2071:
URL: https://github.com/apache/hadoop/pull/2071#issuecomment-3644369356

   We're closing this stale PR because it has been open for 100 days with no 
activity. This isn't a judgement on the merit of the PR in any way. It's just a 
way of keeping the PR queue manageable.
   If you feel like this was a mistake, or you would like to continue working 
on it, please feel free to re-open it and ask for a committer to remove the 
stale tag and review again.
   Thanks all for your contribution.




> Add hadoop process id to the suffix of hadoop-unjar directory
> -------------------------------------------------------------
>
>                 Key: YARN-10313
>                 URL: https://issues.apache.org/jira/browse/YARN-10313
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: client
>    Affects Versions: 3.1.3
>            Reporter: Youquan Lin
>            Assignee: Youquan Lin
>            Priority: Major
>
> We used azkaban to submit many yarn jobs, and the /tmp directory will have 
> many hadoop-unjar directories. Sometimes the hadoop-unjar directory on the 
> azkaban machine takes up a lot of space, but we do not know which process 
> generated this directory. In order to solve this problem, we add the hadoop 
> process id to the suffix of the hadoop-unjar directory.
>  
>  - hadoop process id
>  
> {code:java}
> 10554 org.apache.hadoop.util.RunJar{code}
>  
>  - hadoop-unjar directory name
>  
> {code:java}
> hadoop-unjar8020753511094521686-10554
> {code}



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to