Just a little update on my concurrency issue.
The problem I was having was that under heavy load individual Solr
instances would be slow to respond eventually leading to flapping cluster
membership.
I tweaked a bunch of settings in Linux, Jetty, Solr and within my
application but in the end none
You'll see some lines with three different times in them, "user" "sys"
and "real".
The one that really counts is "real", that's the time that the process was
stopped while GC went on. The "stop" in "Stop the world" (STW) GC
What you're looking for is two things:
1> outrageously long times
and/or
Hi Erick,
You're probably right about it not being a threading issue. In general it
seems that CPU contention could indeed be the issue.
Most of the settings we're using in Solr came "right out of the box"
including Jetty's configuration which specifies:
solr.jetty.threads.min: 10
Hi Pablo,
I'm not sure what settings govern Solr's jetty container.
/opt/solr/server/etc/jetty.xml includes the following:
solr.jetty.threads.min: 10
solr.jetty.threads.max: 1
solr.jetty.threads.idle.timeout: 5000
solr.jetty.threads.stop.timeout: 6
MAX_CONNECTIONS_PER_HOST could
Threads are usually a container parameter I think. True, Solr wants
lots of threads. My return volley would be how busy is your CPU when
this happens? If it's pegged more threads probably aren't really going
to help. And if it's a GC issue then more threads would probably hurt.
Best,
Erick
On
Dave,
there is something similar like MAX_CONNECTIONS and
MAX_CONNECTIONS_PER_HOST which control the number of connections.
Are you leaving open the connection to zookeeper after you establish it?
Are you using the singleton pattern?
2016-12-28 14:14 GMT-03:00 Dave Seltzer
Hi Erick,
I'll dig in on these timeout settings and see how changes affect behavior.
One interesting aspect is that we're not indexing any content at the
moment. The rate of ingress is something like 10 to 20 documents per day.
So my guess is that ZK simply is deciding that these servers are
Dave:
There are at least 4 timeouts (not even including ZK) that can
be relevant, defined in solr.xml:
socketTimeout
connTimeout
distribUpdateConnTimeout
distribUpdateSoTimeout
Plus the ZK timeout
zkClientTimeout
Plus the ZK configurations.
So it would help narrow down what's going on if we
Hello Everyone,
I'm working on a Solr Cloud cluster which is used in a hash matching
application.
For performance reasons we've opted to batch-execute hash matching queries.
This means that a single query will contain many nested queries. As you
might expect, these queries take a while to
