if other folks have seen this either anecdotally or even
> better through some performance testing!
>
> > On May 24, 2024, at 9:12 AM, Tim Funk wrote:
> >
> > solr9 turns security on manager by default. This has a high probability
> of
> > a performance impact..
&
solr9 turns security on manager by default. This has a high probability of
a performance impact..
disable via adding to startup
export SOLR_SECURITY_MANAGER_ENABLED=false
-Tim
On Thu, May 23, 2024 at 11:23 AM elisabeth benoit
wrote:
> Hello,
>
> We've just migrated one of our services from sol
If using java - there is a utility class/method for example
import org.apache.solr.client.solrj.util.ClientUtils;
solrQuery.addFilterQuery("field_name:" +
ClientUtils.escapeQueryChars(field_value));
-Tim
On Tue, Feb 13, 2024 at 1:28 AM Ohms, Jannis
wrote:
> Hi all,
>
> I want to use user suppl
In 9 - The JVM security manager is enabled by default. That might be your
issue.
Disable via adding SOLR_SECURITY_MANAGER_ENABLED=false to your startup
-Tim
On Thu, Oct 12, 2023 at 1:54 PM Natarajan, Rajeswari
wrote:
> Hi,
>
> Does anyone see any query performance degradation from 8.11 to 9.3
Since 9, it’ll listen only to localhost. You need to set an environment
variable
SOLR_JETTY_HOST
also with 9, the security manager is enabled. This may have implications
too depending on your deployment
-Tim
On Sat, Sep 23, 2023 at 2:16 PM Scott Hollenbeck
wrote:
> I'm running a single instan
it before doing more triage.
-Tim
On Mon, Aug 28, 2023 at 7:47 AM Tim Funk wrote:
>
> As for future triage, I'd try the any of the following
> - Change my endpoint and use Http2 ( disable: builder.useHttp1_1(true))
> - Revert to Http2Client and add a timer / logger in exis
I reverted to HttpSolrClient. That seems to have plugged the leak.
As for root cause, I haven't had time to dig farther. Since this happens
regardless of reusing SolrClient vs instantiating a new one, I'm hoping
that's a data point of interest. But as for constructing a "simple" test
to reproduce,
optimistically is
the fix so far.
Client is OpenJDK 11.0.17
-Tim
On Wed, Aug 23, 2023 at 9:46 AM Tim Funk wrote:
> Cool - For now I'll either revert to HttpSolrClient or use a single client
> (depending
> on what I have to refactor)
>
> My only concern with a shared client i
This had been my normal upgrade path now for the major upgrades:
0) Optimistically assume you have all the original data for re-inserts
1) Copy your config to fresh blank instance
2) Verify your solrconfig.xml has an update to date
3) Fix other solrconfig.xml deprecations such as replacing such a
Cool - For now I'll either revert to HttpSolrClient or use a single client
(depending
on what I have to refactor)
My only concern with a shared client is if one calls close() "accidently",
i don't
see an easy way to query the client to see if it was closed so I can
destroy it
and create a new one
End of message is the getSolrClient() . (We have a different core per
language). Also using http 1_1 since we have apache(http) reverse proxy
in front of solr in non-prod tiers and haproxy load balancing in
production.
As I was testing earlier (after initial question), there doesn't
seem to be a
End of message is the getSolrClient() . (We have a different core per
language). Also using http 1_1 since we have apache(http) reverse proxy
in front of solr in non-prod tiers and haproxy load balancing in
production.
As I was testing earlier (after initial question), there doesn't
seem to be a
I've tried to switch from the 8.X to 9.3 solrj client library. At the same
time - I switched to Http2SolrClient since the other was marked deprecated.
We use the client in the pattern ...
try (SolrClient client = createSolrClient()) {
response = client.query(solrQuery);
// do stuff with respo
ially in a standalone environment
available only by app servers?)
-Tim
On Wed, Mar 22, 2023 at 2:50 PM Mikhail Khludnev wrote:
> Hello,
> You can check jstack or Thread Dump in Solr Admin to localize the clog.
>
> On Wed, Mar 22, 2023 at 5:01 PM Tim Funk wrote:
>
> > I ra
he JVM. You might
> try those first.
> If you do a search for JVM java DNS settings it will come up.
>
> On Wed, Mar 22, 2023 at 7:01 AM Tim Funk wrote:
>
> > I ran into an interesting situation today with respect to latency due to
> > failed DNS lookups.
> >
> &g
he JVM. You might
> try those first.
> If you do a search for JVM java DNS settings it will come up.
>
> On Wed, Mar 22, 2023 at 7:01 AM Tim Funk wrote:
>
> > I ran into an interesting situation today with respect to latency due to
> > failed DNS lookups.
> >
> &g
I ran into an interesting situation today with respect to latency due to
failed DNS lookups.
THE SETUP
Using RHEL8, openjdk 11, solr 9.1.1. The solr instance was standalone in a
mostly out of the box config. (No SSL, only http)
I had 3 entries in /etc/resolv.conf and the first one in the list was
17 matches
Mail list logo
