You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@griffin.apache.org by "William Guo (JIRA)" <ji...@apache.org> on 2017/11/29 08:43:00 UTC

[jira] [Comment Edited] (GRIFFIN-71) Failure to submit multiple timing tasks with Livy

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

William Guo edited comment on GRIFFIN-71 at 11/29/17 8:42 AM:
--------------------------------------------------------------

Use 64 bit Java on a 64 bit OS
Decrease Java heap size (-Xmx/-Xms)
Decrease number of Java threads
Decrease Java thread stack sizes (-Xss)
Set larger code cache with -XX:ReservedCodeCacheSize=


was (Author: guoyp):
Use 64 bit Java on a 64 bit OS
Decrease Java heap size (-Xmx/-Xms)
Decrease number of Java threads
Decrease Java thread stack sizes (-Xss)

> Failure to submit multiple timing tasks with Livy
> -------------------------------------------------
>
>                 Key: GRIFFIN-71
>                 URL: https://issues.apache.org/jira/browse/GRIFFIN-71
>             Project: Griffin (Incubating)
>          Issue Type: Bug
>            Reporter: Yang
>         Attachments: hs_err_pid56468.log, spark10err.txt
>
>
> In the client server, using the Livy timer submit 100 monitoring rules, found that Livy will be submitted to the spark cluster on the part of the monitoring task and other tasks fail .We view the Livy log, JVM can't start up, there may be insufficient memory, client log specific memory 32G, please see the attachment.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)