You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mahout.apache.org by "Sean Owen (Commented) (JIRA)" <ji...@apache.org> on 2011/12/06 16:25:40 UTC

[jira] [Commented] (MAHOUT-915) OutOfMemoryError in EigenVerificationJob

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

Sean Owen commented on MAHOUT-915:
----------------------------------

toString() on Vectors writes out everything. I'm almost sure this line should just be removed as you probably never want to log the whole vector. Maybe for debugging, where the data is definitely small... but I hesitate to even say it should be a debug statement since it may stop people from debugging a large job too.
                
> OutOfMemoryError in EigenVerificationJob 
> -----------------------------------------
>
>                 Key: MAHOUT-915
>                 URL: https://issues.apache.org/jira/browse/MAHOUT-915
>             Project: Mahout
>          Issue Type: Bug
>    Affects Versions: 0.6
>            Reporter: Sebastian Schelter
>            Assignee: Sebastian Schelter
>
> I'm getting an OutOfMemoryError in EigenVerificationJob that seems to come from the following lines (200 - 204) that try to print the complete eigenvector to the console.
> {code} 
> EigenVector ev = ...
> log.info("appending {} to {}", ev, path);
> {code} 
> Am I doing something wrong here? Or should we handle this somehow else? I don't want to use another loglevel because of this.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira