[
https://issues.apache.org/jira/browse/SOLR-12156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16417564#comment-16417564
]
Shawn Heisey commented on SOLR-12156:
-------------------------------------
Followup about the "cron" functionality: ALL operating systems come with a
scheduling facility built in. There is no need to have scheduling capability
in Solr.
> "<optimizeConfig>" in solrconfig.xml similar to "<indexConfig>"
> ---------------------------------------------------------------
>
> Key: SOLR-12156
> URL: https://issues.apache.org/jira/browse/SOLR-12156
> 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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
