[ https://jira.codehaus.org/browse/MINDEXER-66?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Igor Fedorenko updated MINDEXER-66: ----------------------------------- Attachment: 0001-MINDEXER-66-provided-a-way-to-customize-IndexWriterC.patch proposed patch > significant increase in used open file handles > ---------------------------------------------- > > Key: MINDEXER-66 > URL: https://jira.codehaus.org/browse/MINDEXER-66 > Project: Maven Indexer > Issue Type: Bug > Affects Versions: 4.1.3, 5.0.0 > Reporter: Igor Fedorenko > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira