[ http://issues.apache.org/jira/browse/DERBY-2107?page=all ]
Knut Anders Hatlen updated DERBY-2107:
--------------------------------------
Attachment: derby-2107-1b.diff
Attaching a new version of the patch to address Dan's comments. (Improved
synchronization and comments.)
If this patch is accepted, I plan to post follow-up patches to address these
issues:
1) There should be some kind of timeout mechanism so that possible deadlocks
are reported.
2) Tool for debugging of deadlocks. A VTI which shows all latches in the
system was suggested on derby-dev.
3) The extra complexity to handle latches should be removed from the lock
manager.
> Move page latching out of the lock manager
> ------------------------------------------
>
> Key: DERBY-2107
> URL: http://issues.apache.org/jira/browse/DERBY-2107
> Project: Derby
> Issue Type: Improvement
> Components: Store, Services, Performance
> Affects Versions: 10.3.0.0
> Reporter: Knut Anders Hatlen
> Assigned To: Knut Anders Hatlen
> Priority: Minor
> Attachments: derby-2107-1a.diff, derby-2107-1a.stat,
> derby-2107-1b.diff
>
>
> Latching of pages could be done more efficiently locally in store than in the
> lock manager. See the discussion here:
> http://thread.gmane.org/gmane.comp.apache.db.derby.devel/33135
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
