[
https://issues.apache.org/jira/browse/SOLR-6761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14221132#comment-14221132
]
Mark Miller commented on SOLR-6761:
-----------------------------------
+1, good idea Tim. I think it can make sense to use commitWithin from the
client exclusively with SolrCloud, but only when a knowledgeable/expert
person/team owns the service. That is very often not the case due to a variety
of reasons in my experience. Solr is often deployed in situations where an
administrator needs to protect the service from a variety of users with varying
expertise.
I agree with Ram though - I think it makes more sense to make sure the client
knows it cannot call commit and adjusts behavior. We just need a useful error
message.
> 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
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
