[
https://issues.apache.org/jira/browse/LUCENE-10171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Gibney resolved LUCENE-10171.
-------------------------------------
Fix Version/s: 9.1
Lucene Fields: (was: New,Patch Available)
Assignee: Michael Gibney
Resolution: Fixed
> Caching issue on dictionary-based OpenNLPLemmatizerFilterFactory
> ----------------------------------------------------------------
>
> Key: LUCENE-10171
> URL: https://issues.apache.org/jira/browse/LUCENE-10171
> Project: Lucene - Core
> Issue Type: Bug
> Components: modules/analysis
> Affects Versions: 9.0, 7.7.3, 8.10
> Reporter: Spyros Kapnissis
> Assignee: Michael Gibney
> Priority: Major
> Fix For: 9.1
>
> Time Spent: 4h 10m
> Remaining Estimate: 0h
>
> When providing a lemmas.txt dictionary file, OpenNLPLemmatizerFilterFactory
> caches internally only the string format of the dictionary, and not the
> DictionaryLemmatizer object. This results in parsing and creating a new
> DictionaryLemmatizer object every time the
> OpenNLPLemmatizerFilterFactory.create() is called.
> In our case, with a large lemmas.txt file (5MB) and the
> OpenNLPLemmatizerFilter used in many fields across our setup and in multiple
> collections (we use Solr), we had several random OOM issues and generally
> high server load due to GC activity. After heap dump analysis we noticed few
> thousands of DictionaryLemmatizer instances of around 80MB each.
> By switching the caching to the DictionaryLemmatizer instead of the String,
> we were able to resolve these issues. I will be attaching a PR for review,
> please let me know of any comments.
> Thanks!
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
