Task #11945 (closed)
Disable concurrent running of Full-text indexer threads
| Reported by: | jballanco-x | Owned by: | jballanco-x |
|---|---|---|---|
| Priority: | blocker | Milestone: | 5.0.0 |
| Component: | General | Version: | 4.4.10 |
| Keywords: | full-text indexing, search | Cc: | atarkowska, ejrozbicki, jamoore, cxallan, jburel |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | 11936 | Remaining Time: | n.a. |
| Sprint: | n.a. |
Description
Evidence suggests that at least part of the reason that the omero.fulltext process eventually becomes unresponsive (see #11936) is that the multiple concurrently-running worker threads end up in a dead-lock situation when one or more of them experiences a heap OOM situation. Running Quartz with concurrency disabled allows new worker threads to continue working even when others have experienced an OOM error.
Change History (3)
comment:1 Changed 10 years ago by jamoore
comment:2 Changed 10 years ago by jamoore
- Resolution set to fixed
- Status changed from new to closed
comment:3 Changed 10 years ago by Josh Ballanco <jballanc@…>
(In [7451fc54ed9381927fe3f8db64f4e80057ce08ea/ome.git] on branch develop) Disable concurrent Quartz scheduling of indexing (see #11945)
With Quartz concurrency enabled, the indexer appears to be getting stuck
in a deadlock when one or more thread experiences an OOM error. Since,
currently, only one thread can index at a time anyway this disables
concurrency in Quartz as a workaround.
PR opened & merged: https://github.com/openmicroscopy/openmicroscopy/pull/2049