-
Notifications
You must be signed in to change notification settings - Fork 500
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Indexing: enable Dataverse to use Solr in a distributed environment #1083
Comments
- added `SolrHostColonPort` config option - Updated Vagrant to allow spin up of multiple VMs
In 57dc52c I enabled a new Here's an example of how to use it: curl -X PUT http://localhost:8080/api/s/settings/:SolrHostColonPort/localhost:8983 @kcondon is this good enough for Dataverse 4.0 or is the use of ZooKeeper a hard requirement? Can we defer ZooKeeper to a future release? I'll put this in QA so you can at least test this new setting. |
OK, this config param works. Will need to test on multi server env. As for whether it is ok for prod, maybe a discussion for others as well? |
Tested on multiple systems and they are both able to update index and see each other's updates. Do not know yet how it performs under load. Benson still hopes we can use Zookeeper and thinks the config isn't that much more involved. Closing as basic functionality has been delivered. |
Right, he showed me we'd start Solr like this:
At least that's how developers would start Solr with a single collection/core/thing. In production ZooKeeper would manage multiple. |
Dataverse is currently coded to connect to solr on localhost. In order to run in a distributed environment, the app needs to be able to connect to a remote solr instance. Ideally this would be done with solr cloud and a zookeeper ensemble. A list of zookeepers would be stored somewhere which the app would use to initialize a CloudSolrServer object.
The text was updated successfully, but these errors were encountered: