[
https://issues.apache.org/jira/browse/MINDEXER-66?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17965272#comment-17965272
]
Olivier Lamy commented on MINDEXER-66:
--------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-indexer#513|https://github.com/apache/maven-indexer/issues/513].
> significant increase in used open file handles
> ----------------------------------------------
>
> Key: MINDEXER-66
> URL: https://issues.apache.org/jira/browse/MINDEXER-66
> Project: Maven Indexer (Moved to GitHub Issues)
> Issue Type: Bug
> Affects Versions: 4.1.3, 5.0.0
> Reporter: Igor Fedorenko
> Assignee: Tamas Cservenak
> Priority: Major
> Fix For: 5.1.0
>
> Attachments:
> 0001-MINDEXER-66-provided-a-way-to-customize-IndexWriterC.patch
>
>
> There is a significant increase in number of open kept opened for each
> IndexingContext between maven-indexer 4.1.2 and 5.0.0. The difference is the
> most pronounced for empty contexts, for which the old version only kept two
> (2) files opened, while the new version keeps eleven (11).
> The root cause appears to be change in default behaviour between Lucene 3.0.3
> and 3.6.1 used by the old and new maven-indexer versions respectively. Lucene
> 3.6.1 provides an API to control how aggressively it aggregates index
> segments into so called "[compound
> files|http://lucene.apache.org/core/3_6_1/fileformats.html#Compound%20Files]";.
> So the solution is to either hardcode aggressive aggregation in
> maven-indexer or provide a way to configure aggregation threshold (or just
> all parameters) on for each IndexingContext.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
