[OOZIE-2406] Completely rewrite GraphGenerator code

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 4.2.0
• Fix Version/s: 5.0.0b1
• Assignee: Andras Piros
• Reporter: Robert Kanter
• Created: 21/Nov/15 01:36
• Updated: 30/Aug/18 12:17
• Resolved: 13/Oct/17 13:15

Description

The Web UI currently generates a graph of the workflow DAG as a png image that it can show to the user (GraphGenerator class). Unfortunately, there are a number of downsides to the current implementation:

1. The image is generated server-side, which doesn't scale well and eats up lots of memory
   • To help combat this issue, we only generate graphs for workflows with less than 25 nodes and we disabled the refresh button in the UI
2. It's slow
3. It uses a library (net.sf.jung from http://jung.sourceforge.net), which hasn't been updated since 2010.
   • This library also has a dependency on a fork of Commons-Collections (net.sourceforge.collections from http://sourceforge.net/projects/collections/), which similarly hasn't been updated since 2010. This is a problem because we can't update Commons-Collections when there are security concerns such as COLLECTIONS-580 (though Oozie is not susceptible to this attack).

It would be good to do a complete rewrite, using a different library and remove Jung and the Commons-Collections fork. Whatever we choose, it should an svg which will draw the image on the browser.

Issue Links

• blocks: OOZIE-3059 Oozie CLI: serve generated workflow graphs
• blocks: OOZIE-3060 Cache generated workflow PNG files
• is duplicated by: OOZIE-1445 Job DAG causes OOM. Reimplement using client side javascript
• is related to: OOZIE-3155 [ui] Job DAG is not refreshed when a job is finished
• relates to: OOZIE-2410 Fork collections-generic
• links to: ReviewBoard link