You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "Paweł Bugalski (Jira)" <ji...@apache.org> on 2021/07/15 08:24:00 UTC
[jira] [Updated] (LUCENE-9869) Allow to configure purge executor in
org.apache.lucene.monitor.Monitor
[ https://issues.apache.org/jira/browse/LUCENE-9869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paweł Bugalski updated LUCENE-9869:
-----------------------------------
Affects Version/s: 8.9
> Allow to configure purge executor in org.apache.lucene.monitor.Monitor
> ----------------------------------------------------------------------
>
> Key: LUCENE-9869
> URL: https://issues.apache.org/jira/browse/LUCENE-9869
> Project: Lucene - Core
> Issue Type: Improvement
> Components: core/other
> Affects Versions: 8.8, 8.9
> Reporter: Paweł Bugalski
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Extend org.apache.lucene.monitor.MonitorConfiguration with an ability to configure how cache purge task is scheduled by org.apache.lucene.monitor.Monitor (aka Luwak). In particular allow to use an external ScheduledExecutor.
> Currently each new instance of org.apache.lucene.monitor.Monitor is creating a new thread in order to schedule a periodic cache purge task. This is fine as long as your application is using a small number of Monitor instances but if for some reason you want to create a large number of Monitor instances (e.g. to separate different business domains) you end up with excessive number of threads created.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org