Task #10749 (closed)
Opened 6 years ago
Closed 3 years ago
Can't have multiple feature calculation scripts running concurrently on the same ContentDB
| Reported by: | spli | Owned by: | spli |
|---|---|---|---|
| Priority: | minor | Milestone: | Partner-1 |
| Component: | General | Version: | 4.4.9 |
| Keywords: | searcher | Cc: | analysis@… |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | n.a. |
Description
The ContentDB is shared per-group (for now). If multiple feature calculation scripts are running concurrently, but which use the same DB, you may trigger
OptimisticLockException: exception ::omero::OptimisticLockException
{
serverStackTrace = ome.conditions.OptimisticLockException: You are not authorized to change the update event for ome.model.annotations.TagAnnotation:Id_6620 from ome.model.meta.Event:Id_1033366 to ome.model.meta.Event:Id_1033364
You may need to reload the object before continuing.
where the TagAnnotation? is attached to the ExperimenterGroup?, and indicates the ContentDB file/version name (the version is incremented with each update and forms part of the filename), hence the concurrent access problem if two updates are made simultaneously.
Change History (4)
comment:1 Changed 6 years ago by spli
- Milestone changed from Unscheduled to OMERO-4.4.10
- Version set to 4.4.9
comment:2 Changed 6 years ago by spli
- Keywords searcher added
comment:3 Changed 6 years ago by spli
- Milestone changed from OMERO-4.4.10 to Partner-1
comment:4 Changed 3 years ago by jamoore
- Resolution set to wontfix
- Status changed from new to closed
Cleaning up searcher backlog.
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
It won't be possible to fix this in the immediate future, but some sort of warning/check would be nice.