You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "purshotam shah (JIRA)" <ji...@apache.org> on 2013/09/13 21:39:51 UTC
[jira] [Updated] (OOZIE-1529) Disabling job DAG display for
workflow having huge actions
[ https://issues.apache.org/jira/browse/OOZIE-1529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
purshotam shah updated OOZIE-1529:
----------------------------------
Description:
1.We should to disable job DAG display for workflow having huge action, probably more than 25.
Job DAQ rendering happens at server side. It's a heavy operation and server goes OOM while generating DAG for workflow having huge actions.
2. There are other UI issue with DAG display.
a.)Client calls to generates DAG two times, 1> while initializing panel. 2> When user clicks Job DAG tab.
We should disable DAG generation while initializing panel. It should be called only when user clicks Job DAG panel.
was:
1.We should to disable job DAG display for workflow having huge action probably more than 25.
Job DAQ rendering happens at server side. It's a heavy operation and server goes OOM while generating DAG for workflow having huge actions.
2. There are other UI issue with DAG display.
a.)Client calls to generates DAG two times, 1> while initializing panel. 2> When user clicks Job DAG tab.
We should disable DAG generation while initializing panel. It should be called only when user clicks Job DAG panel.
> Disabling job DAG display for workflow having huge actions
> ----------------------------------------------------------
>
> Key: OOZIE-1529
> URL: https://issues.apache.org/jira/browse/OOZIE-1529
> Project: Oozie
> Issue Type: Bug
> Affects Versions: trunk
> Reporter: purshotam shah
> Assignee: purshotam shah
> Fix For: trunk
>
>
> 1.We should to disable job DAG display for workflow having huge action, probably more than 25.
> Job DAQ rendering happens at server side. It's a heavy operation and server goes OOM while generating DAG for workflow having huge actions.
> 2. There are other UI issue with DAG display.
> a.)Client calls to generates DAG two times, 1> while initializing panel. 2> When user clicks Job DAG tab.
> We should disable DAG generation while initializing panel. It should be called only when user clicks Job DAG panel.
>
--
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