Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a three-server Solr setup. Server 1 adds new data to the solr index every few minutes. Servers 2 & 3 use the index on server 1 using a file sharing configuration. To get the index updates, servers 2 & 3 run the simple command below every few minutes.

java -jar /path/to/solr/post/file/post.jar

The whole system has been running fine for a few months, but now that our index is growing in size, servers 2 & 3 become unresponsive during or after running the post.jar.

When architecting my solution, it made sense to have one index shared across servers. This allowed for one master data acquirer server and multiple query processing servers. Am I looking at this wrong? Do I need a unique (yet identical) index on each of my query processing Solr servers?


share|improve this question

So I was using my own kludged together multi-server configuration. After a bit of re-architecting, I am now using replication built into Solr 1.4! It is pretty simple to set up. If you are looking to set it up, I can help!


share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.