[ https://issues.apache.org/jira/browse/SOLR-6761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14262417#comment-14262417 ]
ASF subversion and git services commented on SOLR-6761: ------------------------------------------------------- Commit 1648775 from [~thelabdude] in branch 'dev/trunk' [ https://svn.apache.org/r1648775 ] SOLR-6761: Ability to ignore commit and optimize requests from clients when running in SolrCloud mode. > 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 > 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-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org