Details
-
Bug
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
2.3.2, 2.3.3, 2.3.4, 2.3.5, 2.3.6, 2.3.7, 2.4, 2.4.1, 2.4.2, 2.4.3
-
None
Description
The new feature introduced with JCR-3138 may cause resource starvation when enabled. Consider a two node cluster where one of them writes continuously. The second cluster node will start synchronizing those changes from the journal while it holds a read lock on the journal. This lock is never released when new records are continuously available. Write operations on second cluster node will therefore be blocked forever because it cannot get hold of the journal lock.
Attachments
Attachments
Issue Links
- is broken by
-
JCR-3138 Skip sync delay when changes are found
- Closed