Thanks for sharing the information. I think it is a good feature for task
framework. There are two things noticed for roughly scanning the code:
1. For Helix, we are using JAVA 1.7, lamda expression is not supported here.
2. Context should not related to any workflow cloning.
3. JobDAG is already
Hi Xue,
To give you a context, we are using Helix as the backend task execution
engine of Apache Airavata project.
It is sort of a complex process to recreate the same workflow with same
configurations as the workflow generation is done by passing through
different parsers. As a workaround I
Hi Dlmuthu,
Currently, Helix does not support rerun workflow feature. If you would like
to reexecute the workflow, please submit a new one.
Or for your scenario, was the workflow caused by job failing? If yes, you
can increase the number of failed threshold for job level and task level,
which
