Hi All,
Am getting below error in the solr , which is affecting the services which
are accessing the dqmStore. Please suggest if you have come across this
issue.
2022-03-24 08:48:36.629 ERROR (qtp1198197478-620853) [c:dqmStore s:shard1
r:core_node4 x:dqmStore_shard1_replica_n2] o.a.s.
u.SolrCmd
Thanks, Joel, that is exactly what we are doing. We have four shards and
are sharding on the collapse key. Performance is fine (subsecond) as long
as the result set is relatively small. I am really looking for the best
way to ensure that this is always true.
On Wed, Mar 23, 2022 at 10:18 PM Joe
What happens if we need to deploy to production before 8.11.2 is released?
-Original Message-
From: Houston Putman
Sent: Wednesday, March 23, 2022 7:15 PM
To: users@solr.apache.org
Subject: [URL Verdict: Neutral][Non-DoD Source] Re: Solr 8.11.1 upgrading LOG4J
from 2.16 to 2.17
All act
You need to manage your risk in that case --
Which is worse? a potential log4j vulnerability, your own "hacked" solr
war, deploying a pre-release, or delaying the prod rollout?
Will your security scan team allow you to give a mitigation plan and a
timeline for a prod upgrade?
On Thu, Mar 24,
Yeah, that's a tricky problem. Keeping the result set small without losing
results. I don't have an answer except as you already mentioned which would
be to limit the query in some way.
Joel Bernstein
http://joelsolr.blogspot.com/
On Thu, Mar 24, 2022 at 8:24 AM Jeremy Buckley - IQ-C
wrote:
>
Are you determining your "top doc" for each collapsed group based on score?
If your use case is such that you determine the "top doc" based on a static
field with a manageable number of values, you may have other options
available to you. (For some use cases it can be acceptable to "pre-filter"
the
Thanks, Michael. I think this will work, and it is the direction I am
heading. We are collapsing for deduplication, sort of.
We do need to search over the full uncollapsed domain, but I am pretty sure
that nobody needs to see 40 million results, and if they're dumb enough to
enter a query that ma
Thanks for helpful info. I did notice there was no equivalent for
log4j-layout-template-json-2.16.0.
We have changed the query return from XML to JSON, but have done nothing to the
logging.
I will implement this solution after lunch and test it(make sure solr runs and
populates the logs).
B
On 3/24/22 09:38, Heller, George A III CTR (USA) wrote:
BTW, Do you know of anything other than nssm or AlwaysUp that would create a
Windows service to start Solr when the server is rebooted?
NSSM failed our security scan and not sure if cheap bosses want to pay the
small fee for AlwaysUp.
M
Hi Zhiqing,
You can use the 'Stream' menu option on solr console to run the streaming
query. Paste the streaming expression and execute -
Solrj can also execute the expression , here is a page that explains it-
https://lucidworks.com/post/streaming-expressions-in-solrj/
search(collection1,
On 2022-03-24 04:42 +, Sam Lee wrote:
> In my ZooKeeper configuration (zoo.cfg), I have this:
>
> secureClientPort=2182
> #clientPort=2181 # Disabled. Allow secure connections only.
>
> ssl.clientAuth=need
> ssl.keystore.location=/opt/zookeeper/conf/zk-keystore.jks
> ssl.ke
I think I've found the way to connect SolrCloud to an external ZooKeeper
ensemble via SSL.
By default, Solr does not use SSL to connect to ZooKeeper. So if the
ZooKeeper configuration requires SSL for client connections, Solr will
complain like this when it tries to connect to ZooKeeper:
--8<
12 matches
Mail list logo
