12/29/2023 0 Comments Apache lucene increase threads![]() We could use this but it would require a patch to update the tokens we hold in the index. Referred here for how it is done in the spin off. Submitted our approach for this as a contribution. Standard tokenisation of numeric and date fields I have been testing this before adding it. ![]() We have fixed this to clear the thread local on close. See LUCENE-529 and the discussion related to this in the Lucene developer mailing list. This would mitigate this issue but not resolve it. It could be argued we are making too many Indexreaders when they could be reused. I have yet to mimic the isuue in a simple test. The issue can be shown to hold memory in lucene alone but does not give the monotonic increase in memory use. The interaction of lucene with other thread local users seems to be the issue. ![]() This should be held on thread locals as SoftReferences so unused cached information may be garbage collected if required. Lucene is essentially caching information. Objects held on thread locals are garbage collected in an ad hoc way. Lucene uses thread locals in a number of places. The only objects that were accumulating were lucene thread locals. Stress testing showed the memory size of the repository to slowly increase over time.Įventually giving an out of memory error. 8 IndexerReader.exist() can report incorrect results.6 Lock file is not appropriate to signal IPC.2 Standard tokenisation of numeric and date fields.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |