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

Jake Mannix commented on MAHOUT-666:
------------------------------------

You're probably right, actually.  The temp directory which contains the output 
vectors from times() and timesSquared() is ephemerally named, and not even 
saved as a variable.  So there is no code which could know where that file is 
serialized, actually.  Unless it was just looking for all subdirectories 
(sorted by lex) of DistributedRowMatrix#outputTmpBasePath, I guess.

But yeah, I think once MAHOUT-319 is done, we can just set this to be the 
default.  MAHOUT-319 will make sure that the outputs go to sensible places 
which are reusable (and may just be accomplished via essentially "mv <tmpdir> 
<newdir>", and this cleanup code will just be sanity checking to verify the old 
directory is gone).


> DistributedSparseMatrix should clean up after itself when doing times(Vector) 
> and timesSquared(Vector)
> ------------------------------------------------------------------------------------------------------
>
>                 Key: MAHOUT-666
>                 URL: https://issues.apache.org/jira/browse/MAHOUT-666
>             Project: Mahout
>          Issue Type: Bug
>          Components: Math
>    Affects Versions: 0.5
>         Environment: Linux x86_64 2.6.18, Mac OS 10.6 64-bit, Hadoop 0.20.2, 
> Java 1.6
>            Reporter: Jonathan Traupman
>            Assignee: Jake Mannix
>            Priority: Minor
>             Fix For: 0.5
>
>         Attachments: mahout-666.patch
>
>   Original Estimate: 4h
>  Remaining Estimate: 4h
>
> The directories created during the times() and timesSquared() methods in 
> DistributedSparseMatrix leave behind a lot of cruft. While the individual 
> files are tagged with deleteOnExit, but the directories are not. Also, but 
> not deleting them until JVM exit, a job that does repeated matrix/vector 
> multiplies, like DistributedLanczosSolver, creates a lot of temp files that 
> stick around for the whole run, even though the results they contain are read 
> once and then never again. 
> Our cluster admins enforce both file count and size quotas, so since 5 temp 
> files/directories are created on each iteration of DistributedLanczosSolver, 
> we're constantly bumping into the quota with large SVDs. 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to