I'm seeing random crashes in solr 4.0 but I don't have anything to go on
other than "IllegalStateException". Other than checking for corrupt
index and out of memory, what other things should I check?
org.apache.catalina.core.StandardWrapperValve invoke
SEVERE: Servlet.service() for servlet def
My main concern was just making sure we were getting the best search
performance, and that we did not have too many segments. Every attempt I
made to adjust the segment count resulted in no difference (segment
count never changed). Looking at that blog page, it looks like 30-40
segments is prob
On 04/08/2013 09:41 AM, Upayavira wrote:
How many documents do you have? How big are the files on disk?
2,795,601 and the index dir is 50G
Note it says "segments per tier", you may have multiple tiers at play
meaning you can have more than ten segments.
How do I determine how many tiers it h
I'm running solr 4.0. I'm noticing my segments are staying in the 30+
range, even though I have these settings:
10
10
10
false
Can anyone give me some advice on what I should change or check?
It doesn't... you would have to do this with jetty or tomcat. But I
noticed with 4.0 it no longer lives under /admin but rather /solr...and
that means you can't just password-protect it without
password-protecting all of solr. If I am wrong, please let me know...I
would love to protect it someh
dev environment and lock them out of your production
servers totally?
Best
Erick
On Mon, Nov 12, 2012 at 12:41 PM, Michael Long wrote:
I really like the new admin in solr 4.0, but specifically I don't want
developers to be able to unload, rename, swap, reload, optimize, or add
core.
Any i
I really like the new admin in solr 4.0, but specifically I don't want
developers to be able to unload, rename, swap, reload, optimize, or add
core.
Any ideas on how I could still give access to the rest of the admin
without giving access to these? It is very helpful for them to have
access t
We're trying to limit disk space when we optimize since we often hit out
of disk space errors. We plan to add more disks but in the meantime I am
pursing a software solution... in the past we have done multiple passes
by looking at the number of segments and then optimizing down like 16,
8, 4,
