Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Workflows with action policies can deadlock
See original GitHub issueGiven the attached pack (useful for meditation), the system deadlocks when the action _dispatcher_pool (50 entries) gets filled with workflows, and all workflow actions are subsequently held in the _work_buffer queue indefinitely.
One possible solution would be to limit the number of workflows in the _dispatcher_pool to one less than half the total entries, in order to leave room for action execution.
Deadlock pack
This pack contains actions for testing policy deadlock and other behaviors
Actions
delay2- a two second delaydelay20- a twenty second delaydelay2test- a workflow with delay2 followed by delay20
Policies
delay20- limit concurrency to 1delay2test- limit concurrency to 10
Testing
Launch multiple instances of the workflow:
for i inseq 1 100; do st2 action execute deadlock.delay2test; done
Without the delay2test policy, the actions deadlock
Issue Analytics
- State:
- Created 7 years ago
- Comments:22 (21 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@bri365 Thanks for the feedback.
I will also wait on @lakshmi-kannan and others to chime in and if they agree with my proposed approach, I will go ahead and implement it 😃
Awesome, glad to hear it.
And yes, they should be executed in order as requested. Is the ordering issue the same as one described in #2797?
If so, let’s continue there and if not, it’s probably the best to open a new issue and we will have a look 😃