lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shawn Heisey (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-6761) Ability to ignore commit and optimize requests from clients when running in SolrCloud mode.
Date Mon, 23 Jan 2017 14:23:26 GMT

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

Shawn Heisey commented on SOLR-6761:
------------------------------------

bq. When does solr does auto optimize?

Optimize never happens automatically, and it is highly unlikely that it ever will.  Although
it does sometimes have value, in typical situations, the recommendation is to never use the
optimize feature.

On large indexes, the optimize (forceMerge) operation can take a VERY long time, and if any
deleteByQuery calls are used, the optimize will cause the delete (and any subsequent indexing
requests) to block until it is finished.  If deleteByQuery is not used, then indexing requests
are safe to do while the optimize is underway, as of version 4.0.

Please create a new issue to add a configuration option that allows optimizes while blocking
commits, or maybe options to only allow an optimize under certain conditions. I can understand
why [~thelabdude] wrote the feature like it's written.  The basic point of the update processor
is to take away the ability for Solr users to carry out expensive and unnecessary operations.
 Very few operations are as expensive as optimize.

Overall it is better to change the behavior of your clients rather than ignore some of their
requests.  Educate the people that write that code about how your Solr install should be used.

> Ability to ignore commit and optimize requests from clients when running in SolrCloud
mode.
> -------------------------------------------------------------------------------------------
>
>                 Key: SOLR-6761
>                 URL: https://issues.apache.org/jira/browse/SOLR-6761
>             Project: Solr
>          Issue Type: New Feature
>          Components: SolrCloud, SolrJ
>            Reporter: Timothy Potter
>            Assignee: Timothy Potter
>             Fix For: 5.0, 6.0
>
>         Attachments: SOLR-6761.patch, SOLR-6761.patch
>
>
> In most SolrCloud environments, it's advisable to only rely on auto-commits (soft and
hard) configured in solrconfig.xml and not send explicit commit requests from client applications.
In fact, I've seen cases where improperly coded client applications can send commit requests
too frequently, which can lead to harming the cluster's health. 
> As a system administrator, I'd like the ability to disallow commit requests from client
applications. Ideally, I could configure the updateHandler to ignore the requests and return
an HTTP response code of my choosing as I may not want to break existing client applications
by returning an error. In other words, I may want to just return 200 vs. 405. The same goes
for optimize requests.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message