Hi Team,
We have a scenario where we give the Zookeeper FQDN to our Solr Application.
When we use this we are seeing that zookeeper is accepting connections from
all Solr nodes every minute.
When we provide the Zookeeper FQDN with the port number, we are seeing that
there is a single connectio
H. I wonder if a version conflict or perhaps other failure can
somehow cause this. It shouldn't be very hard to add that to my test
setup, just randomly add n _version_ field value.
Erick
On Mon, Oct 1, 2018 at 8:20 AM Erick Erickson wrote:
>
> Thanks. I'll be away for the rest of the week, s
Exactly. I have a node with checksum issue and it is alive which is good
for us since if it goes down one of the shard would be down and thus
outage.
Yes, i agree that we don't get to know if there is node having checksum
issue and thats where we are putting log monitoring which will alert if
"cor
Context filtering, at least using the suggest.cfq parameter, was not
introduced before Solr 6 to my knowledge. As Edwin, I highly recommend
updating.
On Mon, Oct 8, 2018 at 2:20 PM Manu Nair wrote:
> Hi,
>
> I am using Solr 5.1 for my application.
> I am trying to use the autoSuggest feature of
On Sat, Oct 6, 2018 at 1:04 AM Chris Hostetter
wrote:
> Which is to say: there are no explicit convenience methods for it, but you
> can absolutely use the JSON DSL and JSON facets via SolrJ and the
> QueryRequest -- just add the param key=value that you want, where the
> value is the JSON syntax
Hi,
I installed solr as a service onwindows using nssm.
The log4j2.xml file resides in solr\server\resources.
I managed to direct logging of the class "LogUpdateProcessorFactory" to a
new location (a sub-directory in logs).
My problem now is:
- I need to create a new log file for each dih request
