[MAGNOLIA-5362] Introduce mechanism for performing write operations safely in environment with high concurrency Created: 04/Oct/13  Updated: 31/Oct/13  Resolved: 11/Oct/13

Status: Closed
Project: Magnolia
Component/s: templating
Affects Version/s: 4.5
Fix Version/s: 5.1.1

Type: Bug Priority: Neutral
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:
dependency
is depended upon by MAGNOLIA-5351 Moved or deleted items (pages, compon... Closed
is depended upon by MAGNOLIA-5385 Make Autogeneration thread/clustering... Closed
relation
is related to MAGNOLIA-5191 Occasional ItemNotFoundException when... Closed
is related to MAGNOLIA-5432 Do not remove mix:lockable while vers... Closed
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)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Release notes required:
Yes
Sprint: 5.1.1

 Description   

In clustered environment or in environments with high load we have to expect concurrent attempts to create/modify nodes. Currently one such place (specially for programatically created pages) is area auto-generation that is triggered on first page rendering. This issue attempts to provide proof-of-concept for generic locking mechanism that could be used throughout the application.



 Comments   
Comment by Jan Haderka [ 11/Oct/13 ]

Resolved on magnolia-5.1-locking branch.

Generated at Mon Feb 12 04:04:26 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.