[
https://issues.apache.org/jira/browse/UIMA-5048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lou DeGenaro updated UIMA-5048:
-------------------------------
Description:
On uima-ducc-demo we saw one Job that caused PM to OOM. According to the PM
log, the request for Job 784 from PM to Orchestrator to fetch the CommandLine
(comprising the CLASSPATH) resulted in the unexpected value of null.
1. Put more logging code into OR to better understand why a null value was
returned to PM
2. PM should prevent such Jobs Processes from launching, since there is no
command line
3. Increase PM's -Xmx on uima-ducc-demo from 150M to 200M (same as SM and WS)
was:
On uima-ducc-demo we saw one Job that caused PM to OOM. According to the PM
log, the request for Job 784 from PM to Orchestrator to fetch the CommandLine
(comprising the CLASSPATH) resulted in the unexpected value of null.
1. Put more logging code into OR to better understand why a null value was
returned to PM
2. PM should prevent such Jobs from launching
3. Increase PM's -Xmx on uima-ducc-demo from 150M to 200M (same as SM and WS)
> DUCC Orchestrator (OR) record Process Manager (PM) Job CommandLine requests
> ---------------------------------------------------------------------------
>
> Key: UIMA-5048
> URL: https://issues.apache.org/jira/browse/UIMA-5048
> Project: UIMA
> Issue Type: Bug
> Components: DUCC
> Reporter: Lou DeGenaro
> Assignee: Lou DeGenaro
> Fix For: 2.2.0-Ducc
>
>
> On uima-ducc-demo we saw one Job that caused PM to OOM. According to the PM
> log, the request for Job 784 from PM to Orchestrator to fetch the CommandLine
> (comprising the CLASSPATH) resulted in the unexpected value of null.
> 1. Put more logging code into OR to better understand why a null value was
> returned to PM
> 2. PM should prevent such Jobs Processes from launching, since there is no
> command line
> 3. Increase PM's -Xmx on uima-ducc-demo from 150M to 200M (same as SM and WS)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
