[
https://issues.apache.org/jira/browse/LUCENE-8018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16233882#comment-16233882
]
Michael McCandless commented on LUCENE-8018:
--------------------------------------------
bq. We use searchers from multiple threads but we have a lot of them for
consistent pagination. Ours is really an unusual workload for Lucene I guess.
Wow! Impressive :) Lucene's point-in-time searchers make it possible to have
consistent pagination; I'm glad you're using it that way, and I wouldn't say
it's unusual.
But how does that result in 1000s of open {{IndexSearcher}}s at once? Seems
like once an {{IndexSearcher}} is no longer the latest one, and is no longer
involved in an active user session, it can be closed? Do you have a very long
timeout in the user session before you consider the user done searching?
> FieldInfos retains garbage if non-sparse
> ----------------------------------------
>
> Key: LUCENE-8018
> URL: https://issues.apache.org/jira/browse/LUCENE-8018
> Project: Lucene - Core
> Issue Type: Bug
> Components: core/store
> Affects Versions: 6.5
> Environment: Lucene 6.5.0, java 8
> openjdk version "1.8.0_45-internal"
> OpenJDK Runtime Environment (build 1.8.0_45-internal-b14)
> OpenJDK 64-Bit Server VM (build 25.45-b02, mixed mode)
> Reporter: Julian Vassev
> Assignee: Adrien Grand
> Priority: Major
> Labels: easyfix, performance
> Fix For: master (8.0), 7.2
>
> Attachments: LUCENE-8018.patch
>
>
> A heap dump revealed a lot of TreeMap.Entry instances (millions of them) for
> a system with about ~1000 active searchers.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
