So, I have had great success as a SOLR user so far, love its ease of set up. However, I have run into this problem (and this may be more of a Tomcat error; if so, please point me in that direction).
My tomcat application containers have an older lucene library in the common library "lib" folder (2.9) to support some deployed legacy searching applications. The SOLR I'm trying to install in this container has in its .war file WEB-INF/lib all the 4.1 lucene libraries, which if I read the class loader documentation correctly, should override the shared library in tomcat. In fact, when I deploy it, this is the case: the dashboard shows using 4.1.0 lucene implementation. However, if I stop and start the application while the container is running, it CHANGES to 2.9! This mysterious switcheroo caused my slaves to fail after replicating mysteriously over the weekend, as they had been bounced (and thus 2.9) and had received a 4.1 lucene index from the master, and promptly failed hard. Watching one interactively showed it replicating most of an index, then getting an "invalid master" error about 75% in, then going down. Any clues as to why this might be? Should Tomcat be ignoring delegation here, or is it in error? My solution so far has been to move my solr installations off onto "pristine" containers without the lucene library anywhere except the .war file itself. This presents slight problems in our server farm arrangements, and I'd like to not have to "special case" it if possible. Any pointers would be great (even if its to point me at Tomcat's mailing list. :) ) Thanks! Neal Ensor nen...@gmail.com
