[MAGNOLIA-2378] Parallel execution of workflows blocked by exclusive reads/writes during versioning. Created: 18/Sep/08 Updated: 23/Jan/13 Resolved: 23/Sep/08 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | core, workflow |
| Affects Version/s: | None |
| Fix Version/s: | 4.0 |
| Type: | Improvement | Priority: | Major |
| Reporter: | Jan Haderka | Assignee: | Jan Haderka |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||||||
| Description |
|
While you can have multiple workflow running at a same time if there is a long running workflow (e.g. recursive activation) that involves versioning, exclusive read/write locks or some other synchronization causes all the workflow instances to be executed sequentially activating only one piece of content at the time. So such long running workflow would block the others, possibly much shorter ones. |
| Comments |
| Comment by Jan Haderka [ 23/Sep/08 ] |
|
commited as r18219 on 3.6 branch and as r18217 on trunk. |