IllegalStateException
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 default threw exception java.lang.IllegalStateException at org.apache.catalina.connector.ResponseFacade.sendError(ResponseFacade.java:407) at org.apache.solr.servlet.SolrDispatchFilter.sendError(SolrDispatchFilter.java:483) at org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:297) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:857) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:588) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489) at java.lang.Thread.run(Thread.java:662)
Re: Number of segments
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 probably the norm. On 04/08/2013 08:43 PM, Chris Hostetter wrote: : How do I determine how many tiers it has? You may find this blog post from mccandless helpful... http://blog.mikemccandless.com/2011/02/visualizing-lucenes-segment-merges.html (don't ignore the videos! watching them really helpful to understand what he is talking about) Once you've obsorbed that, then please revist your question, specifically Upayavira's key point: what is the problem you are trying to solve? https://people.apache.org/~hossman/#xyproblem XY Problem Your question appears to be an "XY Problem" ... that is: you are dealing with "X", you are assuming "Y" will help you, and you are asking about "Y" without giving more details about the "X" so that we can understand the full issue. Perhaps the best solution doesn't involve "Y" at all? See Also: http://www.perlmonks.org/index.pl?node_id=542341 -Hoss
Re: Number of segments
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 has? There's also, I believe, properties that define the maximum size on disk for a segment and the like that can prevent merges from happening. I just have the defaults...nothing explicitly set Upayavira
Number of segments
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?
Re: Solr Admin Page authentication
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 somehow On 11/16/2012 10:55 AM, Marcin Rzewucki wrote: Hi, Does anybody know if SOLR supports Admin Page authentication ? I'm using Jetty from the latest solr package. I added security option to start.ini: OPTIONS=Server,webapp,security and in configuration file I have (according to Jetty documentation): Test Realm /etc/realm.properties 0 However, it does not seem to be working. Is something missing or it won't work for Solr ? Kind regards.
Re: Admin Permissions
I figured out you can disable the core admin in solr.xml, but then it breaks the admin as apparently it relies on that. I tried tomcat security but haven't been able to make it work I think as this point I may just write a query/debugging app that the developers could use On 11/13/2012 07:12 AM, Erick Erickson wrote: Slap them firmly on the wrist if they do? The Solr admin is really designed with trusted users in mind. There are no provisions that I know of for securing some of the functions. Your developers have access to the Solr server through the browser, right? They can do all of that via URL, see: http://wiki.apache.org/solr/CoreAdmin, they don't need to use the admin server at all. So unless you're willing to put a lot of effort into it, I don't think you really can lock it down. If you really don't trust them to not do bad things, set up a 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 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 to the Query, Analysis, etc.
Admin Permissions
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 to the Query, Analysis, etc.
help with optimizing
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, 2, and 1. We dynamically change the maxSegments through the update handler as we do this. With the 3.3 release using tiered merging, I am wondering if we could be better off doing one pass and using maxMergeAtOnce and segmentsPerTier in solrconfig.xml? Unfortunately I cannot find much documentation on this. Our current settings in solrconfig.xml are: useCompoundFile false mergeFactor 10
