[
https://issues.apache.org/jira/browse/SOLR-1691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12795732#action_12795732
]
Hoss Man commented on SOLR-1691:
--------------------------------
I haven't drilled into the Lucene code to see if this would work, but one idea
would be to have Solr attempt to do a flush on the currently open IndexWriter
in a background thread after any reader is closed.
this could be conditional on the OS type, or on a config option, or if there is
evidence of deletable files (not sure if it's possible to tell from the Lucene
API)
> Deal with deleting old index files in Windows auto-magicly
> ----------------------------------------------------------
>
> Key: SOLR-1691
> URL: https://issues.apache.org/jira/browse/SOLR-1691
> Project: Solr
> Issue Type: Improvement
> Reporter: Hoss Man
>
> Windows users are frequently confused/frustrated by the size of an index
> after making lots of changes/commits because of the way Windows prevents
> files with open handles from being deleted.
> In Lucene-Java, IndexWriter will attempt to delete any old files whenever it
> can, but only on a subsequent change -- we should see if we could add
> something to Solr to try and be more proactive about this...
> http://old.nabble.com/Delete%2C-commit%2C-optimize-doesn%27t-reduce-index-file-size-to26958067.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
