Page History
...
Before plunging into work to make DSpace use the Solr APIs to manage its cores: What's the Simplest Thing That Could Work? We could simply document where to find the current core configurations in DSpace, and instruct the installer to copy them to a place where Solr will find and use them. We could provide some general hints about how to find the destination of these files. Besides being simple, this handles the case in which the people who run DSpace and the people who run Solr are not the same people and issues of access rights ensue.
TODO (not final)
- Complete upgrade of client code to SolrJ 7_x.
- Remove the dspace-solr artifact.
- Work out manual steps for installing empty cores in a free-standing Solr (for a new installation).
- See what manual steps can be moved into Ant's
fresh_install
scripts. - Determine whether schema updates are required.
- Create dump/restore or migration tools for indexes which cannot be recreated (statistics, authority).
- Work out manual steps for copying/migrating/recreating cores with index records into a free-standing Solr.
- See what manual steps can be moved into Ant's
update
scripts. This is only for transition from our outdateddspace-solr
artifact to current stock Solr. - Document the changes to DSpace fresh installation: set up Solr separately if you don't already have it, install cores.
- Document the process for moving existing indexes to free-standing Solr during a DSpace upgrade from 6_x.
Solr Deployment Options
Option |
---|
DSpace version | Repo content | Features | Installation Process | Migration Process | Schema Update Process | Management | Notes | |
---|---|---|---|---|---|---|---|---|
Deploy Solr as Docker Image | 7.preview | New cores only | single server | Core created on container startup Core persisted in docker volumes | N/A | None. A fresh install is required. | N/A | |
Standalone Solr | 7.preview | New cores only | single server | Ant fresh install script needed | N/A | None. Schema update will not be supported until 7.0 | DSpace sysadmin | |
7.0 | New cores Migrated cores No shards | single server | Ant fresh install script needed Auto detection of existing core needed | Migration script needed for statistics and authority. Does this run as part of the install process or is this a maintenance script? Is this a migration process or an import process? | Manually deploy schema updates to Solr. | DSpace sysadmin | ||
8.0+ | New cores Migrated cores No shards | single server | TBD. Note future configuration options. | |||||
Solr Cloud | 7.0 | New cores Migrated cores "Time Routed Aliases" instead of shards | single or multi server | DBA creates cores and installs schemas | Migration script needed for statistics and authority. Does this run as part of the install process or is this a maintenance script? | DBA manually deploys schema updates to Solr. | DBA | |
8.0+ | New cores Migrated cores "Time Routed Aliases" instead of shards | single or multi server | TBD. Note future configuration options. |
Note that there may be reason to run a "degenerate" SolrCloud on a single server. Some APIs are supported only in cloud mode.
Related Tickets and Pull Requests
...