[JCR-3440] Deadlock on LOCAL_REVISION table in clustering environment

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 2.4.3
• Fix Version/s: 2.5.3
• Component/s: clustering
• Environment: Env.1: 4x Linux server CentOS 5 MSSQL 2008 database (production system); Env.2: 2x Linux Ubuntu 10.04 server tested with PostgreSQL 9.1, H2, MSSQL 2008 and mySQL 5.5 (lab system)
• Assignee: Bart van der Schans
• Reporter: Luca Tagliani
• Created: 10/Oct/12 07:37
• Updated: 28/Feb/14 15:14
• Resolved: 22/Jan/13 14:21

Description

When inserting a lot of nodes concurrently (100/200 threads) the system hangs generating a deadlock on the LOCAL_REVISION table.
There is a thread that starts a transaction but the transaction remains open, while another thread tries to acquire the lock on the table.
This actually happen even if there is only a server up but configured in cluster mode.
I found that in AbstractJournal, we try to write the LOCAL_REVISION even if we don't sync any record because they're generated by the same journal of the thread running.

Removing this unnecessary (to me ) write to the LOCAL_REVISION table, remove the deadlock.

Issue Links

• is cloned by: JCR-3738 CLONE - Deadlock on LOCAL_REVISION table in clustering environment