-1 for this. I don’t understand why I can do a optimize over a collection when I want, with or without penalty of performance.
In indexes with a high ratio of deletes the only way to reclaim space is with the optimize command, and yes, sometimes I need to run this command to reclaim 100 or 200G of space from my SSD’s … And yes I know that merge operations removes the deletes, but if you have segments with 100G, and deletes on them you never going to hit this segment in a merge until merge the X others that the index has. Recommendation shouldn’t be enforced, this is the main point of a “recommendation”. Regards, -- /Yago Riveiro On 23 Jan 2017 14:26 +0000, karney luo (JIRA) <[email protected]>, wrote: > > [ > https://issues.apache.org/jira/browse/SOLR-6761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15834652#comment-15834652 > ] > > karney luo commented on SOLR-6761: > ---------------------------------- > > 谢谢您的来信，罗昆仲已经收到 > > > > 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: [email protected] > For additional commands, e-mail: [email protected] >
