[jira] Resolved: (JCR-314) Fine grained locking in SharedItemStateManager

["Marcel Reutegger (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/JCR-314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marcel Reutegger resolved JCR-314.
----------------------------------

       Resolution: Fixed
    Fix Version/s: 1.4

Committed ConfigurableISMLocking.patch in revision: 605173

Please note that there are still some open synchronization issues when using FineGrainedISMLocking!

> Fine grained locking in SharedItemStateManager
> ----------------------------------------------
>
>                 Key: JCR-314
>                 URL: https://issues.apache.org/jira/browse/JCR-314
>             Project: Jackrabbit
>          Issue Type: Improvement
>          Components: jackrabbit-core
>    Affects Versions: 0.9, 1.0, 1.0.1, 1.1, 1.1.1, 1.2.1, 1.2.2, 1.2.3
>            Reporter: Marcel Reutegger
>             Fix For: 1.4
>
>         Attachments: ConfigurableISMLocking.patch, fine-grained-locking-1.4.patch, FineGrainedISMLocking-v2.patch, FineGrainedISMLocking.patch, ISMLocking.patch, writes-per-second.jpg
>
>
> The SharedItemStateManager (SISM) currently uses a simple read-write lock to ensure data consistency. Store operations to the PersistenceManager (PM) are effectively serialized.
> We should think about more sophisticated locking to allow concurrent writes on the PM.
> One possible approach:
> If a transaction is currently storing data in a PM a second transaction may check if the set of changes does not intersect with the first transaction. If that is the case it can safely store its data in the PM.
> This fine grained locking must also be respected when reading from the SISM. A read request for an item that is currently being stored must be blocked until the store is finished.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.