Re: Number of cores per node

Tulsi Das, Thanks for pointing me to the links, but unfortunately these articles/JIRA don't answer my question. Moreover they are over a decade old and much has changed since in the Solr world :) I would still like to know people's experiences handling a large number of Solr cores on a single node

Re: solr-operator formatting of cpu resource

I opened and closed an issue for this. It turns out this happens with standard Deployments objects as well. So, it's something other than the Solr-operator. Sorry for the noise. Joel Bernstein http://joelsolr.blogspot.com/ On Tue, Nov 23, 2021 at 2:17 PM Joel Bernstein wrote: > The more I

Re: solr-operator formatting of cpu resource

The more I think about this issue the more I think the Solr-Operator shouldn't be changing CR objects. My understanding of this is that the operator takes it's direction from the CR object and not the other way around. So for the operator to write back to a CR object, even with equivalent values,

Performance Implications of solr.ICUCollationField

Hi users, I was looking at performance implications on sorting on text-based fields (non-DocValues fields) and wondering how *solr.ICUCollationField* ( https://solr.apache.org/guide/8_8/language-analysis.html#unicode-collation) introduces an issue with thread management and heap consumption (from

Re: solr-operator formatting of cpu resource

A little more testing has shown that the cpu value is only reformatted if it's a multiple of 1000. I'm not sure if the solr-operator can control this or if this part of the go operator framework. But if it's controllable ideally we would probably not reformat the cpu. Joel Bernstein

solr-operator formatting of cpu resource

As part of the collections operator we are working on we need to compare the value of the collection's cpu resource with the value of the underlying SolrCloud cpu resource. What we found is that the SolrCloud cpu resource is being formatted by the Solr operator which makes it tricky to do this

Re: Searcher and autoSoftCommits + softCommit

On 11/23/21 8:31 AM, Dan Rosher wrote: It seems to me that false is not being honored, or does a softCommit always happen on an autoCommit? Cache reloads seems to coincide with solr.autoCommit.maxTime: We have the following solrconfig snippet: ${solr.autoCommit.maxTime:15000}

Searcher and autoSoftCommits + softCommit

Hi, It seems to me that false is not being honored, or does a softCommit always happen on an autoCommit? Cache reloads seems to coincide with solr.autoCommit.maxTime: We have the following solrconfig snippet: ${solr.autoCommit.maxTime:15000} false

EndOfStreamException: Unable to read additional data from server..., likely server has closed socket

Since our upgrade to 8.11.0 we've been getting a lot of warnings with "likely server has closed socket" as part of the description. What do I need to look for in our system configs that would be causing this? WARN  - 2021-11-23 09:47:49.997; org.apache.zookeeper.ClientCnxn; An exception was

Enabling s3 repository clusterwide?

Hello all, I'm trying to setup backup to S3, and see that the plugin must be enabled. The example XML fragments appears to be collection level specific, but I want to enable the plugin globally across all nodes at once. What do I need to specify where? So far, I've only found information

Re: Tesaract.exe

Hi, I assume you are using SolrCell /update/extract to process images and extract text using Teseract OCR. However, teseract.exe is not part of Solr, so I believe your question should be directed towards either the Teseract community or perhaps Tika, or whoever provided you with the

Tesaract.exe

How many processes of Teseract.exe should run simuntaniosly ? How can i configure that? br Gesendet von Mail für Windows

Re: Schema change without restart Solr 6.1.0

Yes, Restart is not needed for schema changes apart from some configuration changes, such as the DataDir location and IndexWriter related settings in solrconfig.xml which can not be changed and made active with a simple RELOAD action. Note :you might have to reindex the data in your collection