[
https://issues.apache.org/jira/browse/MAPREDUCE-7320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17287438#comment-17287438
]
Ahmed Hussein commented on MAPREDUCE-7320:
------------------------------------------
Thanks [~Jim_Brennan].
I see your point.
My thoughts were that leaving the generated data by default increase the disk
utilization.
I face this problem because local hadoop repos sitting on my local machine are
eating large space, especially when I run long sequence of unit tests.
My intuition was that the common case is to run the unit tests, while debugging
output file is less frequent generally speaking. In that case case, the
developer can omit the {{@AfterClass}} that deletes the directory until he is
done with debugging.
P.S: I also found many unit tests that generate data in the home user directory
{{/tmp/hadoop}} which usually never get cleaned. This probably can be a
separate jira to organize the output.
Let me know if you still prefer to keep the data output after the unit test is
done. As you said, having the top level predictable is a good goal by itself.
> 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
