Hi all,
I'm using the 2009-07-29 nightly build of SOLR on a debian box as a non-root user. Seems like the server is constantly going down.
Does anyone have recommendations as to the most stable development release that's compatible with this module in the rc2 version?
It's critical that my search server stay up and running, as it is the backbone of my site. I am far enough into SOLR that I don't really have the option of going to another solution at the moment. I need to find a way to make this stable.
Subscribing to Acquia Search is not in the ballpark for this project budget, as I am indexing about 150,000 nodes and their price block runs $350/yr per 2,000. I'd be paying over $26,000/yr and this is not a commercial site.
Any suggestions to help create maximum stability with minimal cost would be MUCH appreciated.
Thanks,
Noah Lively
Comments
Comment #1
robertdouglass commentedI don't know which nightly is the most stable, but I'd love to have you share the logs of the server that is going down. Maybe we can diagnose the reason. If it is the module code, we should address it. Are you starting your JVM with more than the default amount of memory?
Comment #2
anarchivist commentedWhich servlet container are you using, and what do the logs say when the server goes down?
Comment #3
noahlively commentedErrors seem to vary.
Here is the latest one:
Comment #4
anarchivist commentedWhich servlet container are you using? Are you just using the version of Jetty packaged with Solr?
Comment #5
noahlively commentedYeah, I'm running the example start.jar and using jetty.
Comment #6
anarchivist commentedI'm wondering if this might be related to #529606: schema.xml: update CharStream and EnglishPorter stemmer - can you doublecheck to make sure your Solr schema file has been updated?
Comment #7
noahlively commentedI'll give that a try... but before I do, will this wipe out my existing index?
Comment #8
anarchivist commentedIt shouldn't. Did you upgrade from rc1 to rc2 recently?
Comment #9
robertdouglass commentedMarking as postponed if there is no more info forthcoming.
Comment #10
jpmckinney commentedIt's not even obvious that the failing instance is using this module's config files. We are not responsible for Solr nightly builds.