Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

Oozie can't display the graph cause number of action is more than 25

Solved Go to solution

Oozie can't display the graph cause number of action is more than 25

New Contributor

Hi guys, i have some problem about showing the graph on oozie (Job DAG), cause i have number of action is more than 25.

Is there any solution about this ? because i can't find the configuration to increase the limit of action to show.

13638-oozie.png

1 ACCEPTED SOLUTION

Accepted Solutions

Re: Oozie can't display the graph cause number of action is more than 25

Contributor
10 REPLIES 10

Re: Oozie can't display the graph cause number of action is more than 25

Contributor

Re: Oozie can't display the graph cause number of action is more than 25

New Contributor

@Murali Ramasami is there any option to increase the limit maximum ?

Re: Oozie can't display the graph cause number of action is more than 25

New Contributor

@Murali Ramasami is there any option to increase the limit maximum ?

Re: Oozie can't display the graph cause number of action is more than 25

Contributor

@zaenal rifai No. It is the limitation from oozie UI.

Re: Oozie can't display the graph cause number of action is more than 25

Contributor

@zaenal rifai If this helped, please vote/accept best answer.

Re: Oozie can't display the graph cause number of action is more than 25

Mentor

13679-many3.png

@zaenal rifai

the solution to your problem is to wait for Ambari 2.5 and use Workflow manager view. I just tested a workflow with 26 actions and it displayed well, except it's hard to see with so many actions. I attached screenshots to my response. The other option is of course to file a jira and either submit a patch or wait for community to work on the jira. I say use Workflow Manager when it comes out. The collapsed view is from the original design of the flow, the image titled many and many2 is result of running the workflow and representing the flow graph, which is what you're trying to do. With WFM, you actually can visually display your flow graph before and after the execution of the flow.

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<workflow-app xmlns="uri:oozie:workflow:0.5" name="Workflow3">
    <start to="email_1"/>
    <action name="email_1">
        <email xmlns="uri:oozie:email-action:0.2">
            <to>address@hortonworks.com</to>
            <subject>1</subject>
            <body>1</body>
        </email>
        <ok to="email_2"/>
        <error to="kill"/>
    </action>
    <action name="email_2">
        <email xmlns="uri:oozie:email-action:0.2">
            <to>address@hortonworks.com</to>
            <subject>1</subject>
            <body>1</body>
        </email>
        <ok to="email_3"/>
        <error to="kill"/>
    </action>
    <action name="email_3">
        <email xmlns="uri:oozie:email-action:0.2">
            <to>address@hortonworks.com</to>
            <subject>1</subject>
            <body>1</body>
        </email>
        <ok to="email_4"/>
        <error to="kill"/>
    </action>
    <action name="email_4">
        <email xmlns="uri:oozie:email-action:0.2">
            <to>address@hortonworks.com</to>
            <subject>1</subject>
            <body>1</body>
        </email>
        <ok to="email_5"/>
        <error to="kill"/>
    </action>
    <action name="email_5">
        <email xmlns="uri:oozie:email-action:0.2">
            <to>address@hortonworks.com</to>
            <subject>1</subject>
            <body>1</body>
        </email>
        <ok to="email_6"/>
        <error to="kill"/>
    </action>
    <action name="email_6">
        <email xmlns="uri:oozie:email-action:0.2">
            <to>address@hortonworks.com</to>
            <subject>1</subject>
            <body>1</body>
        </email>
        <ok to="email_7"/>
        <error to="kill"/>
    </action>
    <action name="email_7">
        <email xmlns="uri:oozie:email-action:0.2">
            <to>address@hortonworks.com</to>
            <subject>1</subject>
            <body>1</body>
        </email>
        <ok to="email_8"/>
        <error to="kill"/>
    </action>
    <action name="email_8">
        <email xmlns="uri:oozie:email-action:0.2">
            <to>address@hortonworks.com</to>
            <subject>1</subject>
            <body>1</body>
        </email>
        <ok to="email_9"/>
        <error to="kill"/>
    </action>
    <action name="email_9">
        <email xmlns="uri:oozie:email-action:0.2">
            <to>address@hortonworks.com</to>
            <subject>1</subject>
            <body>1</body>
        </email>
        <ok to="email_10"/>
        <error to="kill"/>
    </action>
    <action name="email_10">
        <email xmlns="uri:oozie:email-action:0.2">
            <to>address@hortonworks.com</to>
            <subject>1</subject>
            <body>1</body>
        </email>
        <ok to="email_11"/>
        <error to="kill"/>
    </action>
    <action name="email_11">
        <email xmlns="uri:oozie:email-action:0.2">
            <to>address@hortonworks.com</to>
            <subject>1</subject>
            <body>1</body>
        </email>
        <ok to="email_12"/>
        <error to="kill"/>
    </action>
    <action name="email_12">
        <email xmlns="uri:oozie:email-action:0.2">
            <to>address@hortonworks.com</to>
            <subject>1</subject>
            <body>1</body>
        </email>
        <ok to="email_13"/>
        <error to="kill"/>
    </action>
    <action name="email_13">
        <email xmlns="uri:oozie:email-action:0.2">
            <to>address@hortonworks.com</to>
            <subject>1</subject>
            <body>1</body>
        </email>
        <ok to="email_14"/>
        <error to="kill"/>
    </action>
    <action name="email_14">
        <email xmlns="uri:oozie:email-action:0.2">
            <to>address@hortonworks.com</to>
            <subject>1</subject>
            <body>1</body>
        </email>
        <ok to="email_15"/>
        <error to="kill"/>
    </action>
    <action name="email_15">
        <email xmlns="uri:oozie:email-action:0.2">
            <to>address@hortonworks.com</to>
            <subject>1</subject>
            <body>1</body>
        </email>
        <ok to="email_16"/>
        <error to="kill"/>
    </action>
    <action name="email_16">
        <email xmlns="uri:oozie:email-action:0.2">
            <to>address@hortonworks.com</to>
            <subject>1</subject>
            <body>1</body>
        </email>
        <ok to="email_17"/>
        <error to="kill"/>
    </action>
    <action name="email_17">
        <email xmlns="uri:oozie:email-action:0.2">
            <to>address@hortonworks.com</to>
            <subject>1</subject>
            <body>1</body>
        </email>
        <ok to="email_18"/>
        <error to="kill"/>
    </action>
    <action name="email_18">
        <email xmlns="uri:oozie:email-action:0.2">
            <to>address@hortonworks.com</to>
            <subject>1</subject>
            <body>1</body>
        </email>
        <ok to="email_19"/>
        <error to="kill"/>
    </action>
    <action name="email_19">
        <email xmlns="uri:oozie:email-action:0.2">
            <to>address@hortonworks.com</to>
            <subject>1</subject>
            <body>1</body>
        </email>
        <ok to="email_20"/>
        <error to="kill"/>
    </action>
    <action name="email_20">
        <email xmlns="uri:oozie:email-action:0.2">
            <to>address@hortonworks.com</to>
            <subject>1</subject>
            <body>1</body>
        </email>
        <ok to="email_21"/>
        <error to="kill"/>
    </action>
    <action name="email_21">
        <email xmlns="uri:oozie:email-action:0.2">
            <to>address@hortonworks.com</to>
            <subject>1</subject>
            <body>1</body>
        </email>
        <ok to="email_22"/>
        <error to="kill"/>
    </action>
    <action name="email_22">
        <email xmlns="uri:oozie:email-action:0.2">
            <to>address@hortonworks.com</to>
            <subject>1</subject>
            <body>1</body>
        </email>
        <ok to="email_23"/>
        <error to="kill"/>
    </action>
    <action name="email_23">
        <email xmlns="uri:oozie:email-action:0.2">
            <to>address@hortonworks.com</to>
            <subject>1</subject>
            <body>1</body>
        </email>
        <ok to="email_24"/>
        <error to="kill"/>
    </action>
    <action name="email_24">
        <email xmlns="uri:oozie:email-action:0.2">
            <to>address@hortonworks.com</to>
            <subject>1</subject>
            <body>1</body>
        </email>
        <ok to="email_25"/>
        <error to="kill"/>
    </action>
    <action name="email_25">
        <email xmlns="uri:oozie:email-action:0.2">
            <to>address@hortonworks.com</to>
            <subject>1</subject>
            <body>1</body>
        </email>
        <ok to="email_26"/>
        <error to="kill"/>
    </action>
    <action name="email_26">
        <email xmlns="uri:oozie:email-action:0.2">
            <to>address@hortonworks.com</to>
            <subject>1</subject>
            <body>1</body>
        </email>
        <ok to="end"/>
        <error to="kill"/>
    </action>
    <kill name="kill">
        <message>${wf:errorMessage(wf:lastErrorNode())}</message>
    </kill>
    <end name="end"/>
</workflow-app>



many2.pngmany.png

Re: Oozie can't display the graph cause number of action is more than 25

This is maybe a bug, I see the same error on my HDP-2.5.0 Oozie, with only 1 action. Do you really have more than 25 actions? On a HDP-2.5.3 cluster it works fine with 1 action. If you really have more than 25 actions then it won't work as shown by @Murali Ramasami

Re: Oozie can't display the graph cause number of action is more than 25

Okay, actually I had some mess with my Oozie folders, and I couldn't stop Oozie, because /var/tmp/oozie was missing. After adding it and restarting Oozie I can see a 1 action DAG. So, again, if you have less than 25 actions make sure your Oozie is healthy, restart it and retry.

Re: Oozie can't display the graph cause number of action is more than 25

Contributor

Hi,I have the same question,same error with one 1 action,I try your method,but it didn't work!

Don't have an account?
Coming from Hortonworks? Activate your account here