lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Erick Erickson (JIRA)" <>
Subject [jira] [Commented] (SOLR-12156) "<optimizeConfig>" in solrconfig.xml similar to "<indexConfig>"
Date Thu, 19 Jul 2018 23:43:00 GMT


Erick Erickson commented on SOLR-12156:

I'll assign this to myself and close it in a couple of days if there are no objections. As
of Solr 7.5, TieredMergePolicy will respect max segment sizes. Couple that with the new ability
to control the percentage of deleted documents  in the index and I don't think the ideas here
are needed.

As far as users shooting themselves in the foot, disabilng user-driven optimizations should
is an option as Shawn points out.

> "<optimizeConfig>" in solrconfig.xml similar to "<indexConfig>"
> ---------------------------------------------------------------
>                 Key: SOLR-12156
>                 URL:
>             Project: Solr
>          Issue Type: Wish
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: config-api
>            Reporter: Indranil Majumder
>            Priority: Major
> It would be great to have the below config parameters in solrconfig.xml :-
>  # maxMergedSegmentMB (same as in TieredMergePolicy)
>  # maxOptimizeSegments (same as in solrjClient.optimize( *waitFlush,**waitSearcher* ,{color:#FF0000}*maxSegments*{color}))
>  # expungeDeletes (true/false)
>  # optimizeTimeout(in minutes)
>  # disableExlicitOptimize (disable all solrClient call to optimize )
>  ## optimizeJobCron - associated to disableExlicitOptimize where optimization can be
carried out at a maintenance period defined by the cron expression.
> This in turn needs to be respected by DirectUpdateHandler2 or any other handler trying
to optimize the index

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message