No need to restart when there has been an index change... just send a commit message and Solr will open a new searcher.
If there have been schema changes, Solr will need to be restarted. -Yonik On 7/18/07, Matt Mitchell <[EMAIL PROTECTED]> wrote:
Hi, I'm currently working on an application which is living in a clustered server environment. There is a hardware based balancer, and each node in the cluster has a separate install of Solr. The application code and files are on a NFS mount, along with the "solr/ home". The first node has been acting as the master. My question is about reindexing, and even schema updates in some circumstances. For a reindex, I post to Solr on the master node and then restart the remaining nodes. Is there a better way to do this? For a schema update, I stop the master, delete the data/index dir, start solr and then post to Solr on the master node. Then I restart the remaining nodes. Is there a better way to do this? Any tips, feedback or what have are much appreciated! Matt
