Long running workflows on cluster | Community
Skip to main content
A
Anonymous
October 16, 2015
Solved

Long running workflows on cluster

  • October 16, 2015
  • 5 replies
  • 1529 views

Hi

We have a long running workflow (loop) on clustered author instance. When we are running this workflow on master, we can see that the workflow is also running on slaves as well. I don't think this is correct. Workflow should by default be cluster aware and should only run on master. 

How can I restrict a workflow to only run on one node.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Sham_HC

If aem 5.6 file daycare & request for hotfix CQ560_HF_3314

5 replies

A
Anonymous
October 16, 2015

I didn't find any solution from daycare and now I am changing the design. Will avoid internal loop inside workflow (no goto).

Sham_HC
Sham_HCAccepted solution
Level 10
October 16, 2015

If aem 5.6 file daycare & request for hotfix CQ560_HF_3314

T
tyatyushkin
October 16, 2015

Vishal, does ussue exist on CQ5.6.1?

One another question:
I have publish clustering on CQ5.6.1.
And I can see that workflows running on both MASTER and SLAVE nodes.
Also I can see workflows marked as "STALE", but when I open history of the workflow I see "Workflow Completed".
Any ideas?
Thanks

A
Anonymous
October 16, 2015

Sham HC wrote...

If aem 5.6 file daycare & request for hotfix CQ560_HF_3314

 

 

This hotfix is only for DAM assets.

A
Anonymous
October 16, 2015

My Issue is still open with Adobe. The hotfix that Sham HC has suggested is only applicable for dam assets.

For your question, few things you need to check

  1. How you reach to the conclusion that the workflow is running on both node ?
  2. If you have any confusion regarding the status of workflow check the following path in CRX "/etc/workflow/instances/YYYYMMDD/INSTANCEID/YOURWFINSTANCE". 

 

Thanks

-Vishal

Terms & ConditionsAccessibility statement

Loading footer...