SolrClient implements Closable which means it needs to be closed when
you're done with it or you leak resources.
On Thu, Feb 17, 2022 at 6:47 PM Steven White wrote:
>
> Hi everyone,
>
> I wanted to follow up on this topic, thank everyone for your feedback and
> share with you what fixed my issue
Hi everyone,
I wanted to follow up on this topic, thank everyone for your feedback and
share with you what fixed my issue in case anyone else runs into it.
Rather than reply to each feedback, I figured it is best to summarize it
here.
The code I'm dealing with is a legacy that I inherited. Thus,
Hi All,
We have Solr cloud setup, version : 8.8.2
I was able to set the stop port and everything was working fine.
Initial setup was to use SSL, now we need to turn off SSL and so we changed
all the configs in solr.in.cmd
when we stop the first instance in the server using the command solr stop
Hi,
I've got some new updates on this issue. We found out that the host we are
using has SELinux enabled. It is also a FIPS enabled environment. So we had
one of our admins apply the necessary SELinux settings to allow Solr which
got rid of the SELinux errors we saw. Now we're trying to figure out
I just happened to be looking into this as well. I assume you've seen the
refguide documentation:
https://solr.apache.org/guide/8_11/query-settings-in-solrconfig.html#user-defined-caches
Normally one would not configure a user-defined cache except in support of
other custom plugins/components. e.g
Hello Solr community,
I am working with Solr 7.7 and I have been experimenting with the geodist
function. The issue is that I can not directly pass the parameters to the
function, so it only works with general parameters in the request. For
example these queries work:
- select?pt=7.87104,4.49698&q
Hi All,
I was able to set the stop port and everything was working fine.
Initial setup was to use SSL, now we need to turn off SSL and so we changed
all the configs in solr.in.cmd
when we stop the first instance in the server using the command solr stop
-p 3883, node 3883 goes down and 9883 is up
