Re: simple production set up

2010-11-19 Thread Markus Jelsma
Please stay on the list. Anyway, it's a matter of not exposing certain request handlers to the public. If you have a master/slave set up, you can remove the update handlers from your public facing slave (or hide it behind HTTP auth in your proxy). The same goes for other defined request handler

Re: simple production set up

2010-11-18 Thread Markus Jelsma
Hi, It's a common practice not to use Solr as a frontend. Almost all deployed instances live in the backend near the database servers. And if Solr is being put to the front, it's still being secured by a proxy. Setting up staging and production instances depend on your need. If the load is sma

simple production set up

2010-11-18 Thread lee carroll
Hi I'm pretty new to SOLR and interested in getting an idea about a simple standard way of setting up a production SOLR service. I have read the FAQs and the wiki around SOLR security and performance but have not found much on a best practice architecture. I'm particularly interested in best practi