I actually have read that and I have Solr up and running on Tomcat. I didn't realize that it was example/ including Jetty, etc. that was being recommended against, but the $SOLR_HOME, which I created by copying example/solr/
Thanks for the tips on upgrading. I'll keep that in our documentation. Brandon Ramirez | Office: 585.214.5413 | Fax: 585.295.4848 Software Engineer II | Element K | www.elementk.com -----Original Message----- From: Erick Erickson [mailto:erickerick...@gmail.com] Sent: Thursday, December 29, 2011 8:18 AM To: solr-user@lucene.apache.org Subject: Re: Best practices for installing and maintaining Solr configuration This should help: http://wiki.apache.org/solr/SolrTomcat The difference here is that you're not copying the example directory, you're copying the example/solr directory. And this is just basically to get the configuration files and directory structure right. You're not copying executables, jars, wars, or any of that stuff from example. You get the war file from the dist directory and that should contain all the executables & etc. As to your other questions: 1> If at all possible, upping the match version and reindexing are good things to do. 2> It's also a good idea to update the config files. Alternatively, you can diff the config files between releases to see what the changes are and selectively add them to your config file. But you should test, test, test before rolling out into prod. My rule of thumb for upgrading is to just not upgrade minor releases unless there are compelling reasons. The CHANGES.txt file will identify major additions. There are good reasons not to get too far behind on major (i.e. 3.x -> 4.x) releases, the primary one being that Solr only makes an effort to be backwards-compatible through one major release. i.e. 1.4 can be read by 3.x (there was no 2.x Solr release). But no attempt will be made to by 4.x code to read 1.x indexes. Hope this helps Erick On Wed, Dec 28, 2011 at 8:49 AM, Brandon Ramirez <brandon_rami...@elementk.com> wrote: > Hi List, > I've seen several Solr developers mention the fact that people often copy > example/ to become their solr installation and that that is not recommended. > We are rebuilding our search functionality to use Solr and will be deploying > it in a few weeks. > > I have read the README, several wiki articles, mailing list and browsed the > Solr distribution. The example/ directory seems to be the only configuration > I can find. So, I have to ask: what is the recommended way to install Solr? > > What about maintaining it? For example, Is it wise to up the > luceneMatchVersion and re-index with every upgrade? When new configuration > options are added in new versions of Solr, should we worry about updating our > configuration to include them? I realize these may be vague questions and > the answers could be case-by-case, but some general or high-level > documentation may help. > > Thanks! > > > Brandon Ramirez | Office: 585.214.5413 | Fax: 585.295.4848 Software > Engineer II | Element K | www.elementk.com<http://www.elementk.com/> >
