Task #1266 (closed)
Opened 15 years ago
Closed 15 years ago
Write-operations may should use two transactions
| Reported by: | jamoore | Owned by: | jamoore |
|---|---|---|---|
| Priority: | critical | Milestone: | OMERO-Beta4.1 |
| Component: | Performance | Version: | 3.0-M1 |
| Keywords: | n.a. | Cc: | cxallan, jrswedlow, jburel |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | n.a. |
Description
Currently, write-operations first query the current user state in BasicSecuritySystem.loadEventContext and then proceed with the UPDATEs. This leaves all the auth tables in <IDLE> in transaction.
Change History (2)
comment:1 Changed 15 years ago by jmoore
- Cc cxallan jrswedlow jburel added
comment:2 Changed 15 years ago by jmoore
- Resolution set to fixed
- Status changed from new to closed
Other than the warnings mentioned in #1254, this seems to be working fine in 4.0. Closing.
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
This ticket is directly related to #1254. Everything that prolonged a transaction (indexing, increased auth, etc), extended the periods of <IDLE> in transaction which lead to the deadlocks.
Adding the deferred constraints helped but did not solve the problem. The only solution I've found to date (other than re-designing a sizable port of the tx code) is to slip a COMMIT;BEGIN into EventHandler for all read-write calls.
Debating adding this to 4.0.