[
https://issues.apache.org/jira/browse/MAPREDUCE-7320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17287385#comment-17287385
]
Jim Brennan commented on MAPREDUCE-7320:
----------------------------------------
[~ahussein] Thanks for cleaning this up. But I always thought keeping these
around was intentional? If you get a failure, it is sometimes useful to be
able to find the logs of the mini cluster (especially job/container logs).
In cases like this, you would want to make sure the top level directory is
predictable (which you have done), but you would want to delete them at the
beginning of the test instead of the end.
This would still leave a bunch of files around after running the unit tests,
but a subsequent run would first delete the old stuff. What do you think?
> ClusterMapReduceTestCase does not clean directories
> ---------------------------------------------------
>
> Key: MAPREDUCE-7320
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-7320
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Reporter: Ahmed Hussein
> Assignee: Ahmed Hussein
> Priority: Major
> Labels: pull-request-available
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Running Junits that extend {{ClusterMapReduceTestCase}} generate lots of
> directories and folders without cleaning them up.
> For example:
> {code:bash}
> men test -Dtest=TestMRJobClient{code}
> generates the following directories:
> {code:bash}
> - target
> -+ ConfigurableMiniMRCluster_315090884
> -+ ConfigurableMiniMRCluster_1335188990
> -+ ConfigurableMiniMRCluster_1973037511
> -+ test-dir
> -+ dfs
> -+ hadopp-XYZ-01
> -+ hadopp-XYZ-02
> -+ hadopp-XYZ-03
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org
