You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sqoop.apache.org by "Hari Shreedharan (JIRA)" <ji...@apache.org> on 2012/12/15 23:28:12 UTC

[jira] [Commented] (SQOOP-772) OutOfMemory from document generation

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

Hari Shreedharan commented on SQOOP-772:
----------------------------------------

+1. Looks good. We did the same in Flume as well - seems like Sphinx uses Jython which uses requires higher MaxPermSize.
                
> OutOfMemory from document generation
> ------------------------------------
>
>                 Key: SQOOP-772
>                 URL: https://issues.apache.org/jira/browse/SQOOP-772
>             Project: Sqoop
>          Issue Type: Bug
>            Reporter: Bilung Lee
>            Priority: Trivial
>         Attachments: bugSQOOP-772.patch
>
>
> OutOfMemory may be thrown from documentation generation during build process.
> One workaround is to increase allowed memory space:
> export MAVEN_OPTS="-Xmx512m -XX:MaxPermSize=128m"

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira