We simply deleted the earlier versions of the log4j jars from the
server/lib/ext folder and replaced them with 2.17.1 versions, and restarted
Solr.
Works normally
> On 11 Mar 2022, at 13:29, Heller, George A III CTR (USA)
> wrote:
>
> We have a Solr 8.11.1 installation we are getting ready t
Apologies for any typos, using a phone
> On 13 Dec 2021, at 14:27, Horton, Alan
> wrote:
>
> Initially a series of sessionExpiredExceptions:
>
> Eventually a timeoutException:
>
>
> Thanks
>
>
> -Original Message-
> From: Gus Heck
> Sent: 13 December 2021 14:10
> To: users@sol
This threw me for a while when I worked on it.
Visit this page
https://cwiki.apache.org/confluence/plugins/servlet/mobile?contentId=55153140#content/view/55153140
You need to treat Solr as a Zookeeper client and add the six system properties
it recommends for ziCli.sh to your Solr.in.sh or simila
I remember we had an issue with duplicates being created when we moved from
6.6.1 to 8.4.0. One of our cores had a dynamic field definition which was
stored but not indexed.
We would add an existing document to the core and a duplicate of it would
appear; add it again and another duplicate.
We
HI Rob, thanks for your help.
> Do you know if in case of failure (initFailures not empty)
> /solr/admin/cores changes the http status code of the response in 500 (or
> everything that is not 200) ?
>
>> On Wed, Oct 27, 2021 at 6:13 PM Robert Pearce wrote:
>>
>>
Take a look at the cores REST API, something like
http://localhost:8983/solr/admin/cores?action=STATUS&wt=json
Any failed cores will be in ‘initFailures’; cores which started will be under
“status”
Rob
> On 27 Oct 2021, at 16:28, Vincenzo D'Amore wrote:
>
> Hi all,
>
> when a Solr instance
Hello,
I have a question regarding Solr and Zookeeper configured for SSL. Simply, does
Solr default to non-SSL when connecting with the Zookeeper secure port on
localhost?
Solr 8.9, Zookeeper 3.6.2
One Zookeeper instance configured for SSL
One Solr instance configured for SSL, pointing at ZK se
