[ 
https://issues.apache.org/jira/browse/SOLR-12156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16418507#comment-16418507
 ] 

Indranil Majumder commented on SOLR-12156:
------------------------------------------

The use case for these configurations is, as a Solr master administrator, I 
want to keep control on the optimization asked for on my index.

There are multiple data transformers which connects to this master using SolrJ. 
I do not have full control on them. But if a novice developer calls optimize 
after each commit, I want my configurations to protect my index from that.

Regarding the CRON, yes my ask is similar to the DocDeletion policy available 
via updateRequestProcessorChain. Just like doc deletion I want to configure 
internally a downtime where the optimize will auto initiate and the system will 
be able to give it enough time to complete (may be late sunday night, once a 
week).

> "<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]

Reply via email to