0

I have a server which has a Solr Environment hosted on it. I want to run a weekly update of the data that our Solr database contains.

I have a couple solutions but I was wondering whether one is possible and if it is which one would be better:

My first solution is to have 2 Servers with a Solr environment on both and when one is updating you just switch the url using to connect to Solr and connect to the other one.

My other solution is the one I am not sure how to do. Is there a way to switch the datasource that a Solr environment looks at without restarting it or cutting out any current searches.

If anyone has any ideas it would be much appreciated.

Brian Tompsett - 汤莱恩
  • 5,753
  • 72
  • 57
  • 129
Tobias
  • 67
  • 1
  • 2
  • 6

1 Answers1

3

Depending on the size of the data, you can probably just keep the Solr core running while doing the update. First issue a delete, then index the data and finally commit the changes. The new index state won't be seen before the commit is issued, which allows you to serve the old data while waiting for the indexing to complete.

Another option is to use the core admin to switch cores as you mentioned, similar to copying data into other cores (drop the mergeindex command).

If you're also talking about updating and upgrading the actual Solr version or application server while still serving content, having a second server that replicates the index from the master is an easy way to get more redundancy. That way you can keep serving queries from the second server while the first one is being maintained and then do it the other way around. Point your clients to an HTTP load balancer, and take the maintained server out of the list of servers serving requests while it's down. This will also make you resistant against single hardware failures, etc.

There's also the option of setting up SolrCloud, but that might require a bit more restructuring.

Community
  • 1
  • 1
MatsLindh
  • 49,529
  • 4
  • 53
  • 84