Bug #28733

Implement LockManager for avoiding Race Conditions

Added by Sebastian Kurfuerst almost 5 years ago. Updated almost 4 years ago.

Status:Resolved Start date:2011-08-04
Priority:Must have Due date:
Assigned To:- % Done:

100%

Category:Cache
Target version:TYPO3 Flow Base Distribution - 1.0 beta 1
PHP Version: Complexity:
Has patch: Affected Flow version:

Related issues

related to TYPO3.Flow - Task #3755: Concurrency stress testing and cache mechanism New 2009-06-25
related to TYPO3.Flow - Bug #27989: Wrong check in our atomic writes code Resolved 2011-07-08

Associated revisions

Revision 71d18d4c
Added by Robert Lemke almost 4 years ago

[FEATURE] Re-introduce Lock Manager

This reintroduces the Lock Manager which locks the whole site while
compile time commands are executed. The Lock Manager will protect
applications running in Production context against race conditions
during cache warming and other code manipulating commands.

The Lock Manager is not active in Development or Testing context.

Change-Id: I764d8df0a31aa8bd84463be88f7375e843de4ef9
Resolves: #28733

History

#1 Updated by Mr. Hudson almost 4 years ago

  • Status changed from New to Under Review

Patch set 1 of change I764d8df0a31aa8bd84463be88f7375e843de4ef9 has been pushed to the review server.
It is available at http://review.typo3.org/4550

#2 Updated by Mr. Hudson almost 4 years ago

Patch set 2 of change I764d8df0a31aa8bd84463be88f7375e843de4ef9 has been pushed to the review server.
It is available at http://review.typo3.org/4550

#3 Updated by Robert Lemke almost 4 years ago

  • Status changed from Under Review to Resolved
  • % Done changed from 0 to 100

Also available in: Atom PDF