[
https://issues.apache.org/jira/browse/SOLR-6761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14248748#comment-14248748
]
Hoss Man commented on SOLR-6761:
--------------------------------
i don't see how it's really any differnet then anything else we expect "solr
admins" to edit in their solrconfig.xml (like enableStreaming, whether the
/update should have any defaults on it, etc...)
but if you really want it to be sysprop driven, that can still be done via the
enable property...
{code}
<processor class="solrIgnoreCommitUpdateProcessorFactory"
enable="${solr.ignore.explicit.commit:false}">
...
</processor>
{code}
> 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
> Attachments: 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: [email protected]
For additional commands, e-mail: [email protected]
