Skip to content

Solr stack documentation

Default core

Since 1.1.0 we automatically create a default solr core named default when no cores found.

Solr can be configured via environment variables available listed at https://github.com/wodby/solr

Creating solr core

You can create new cores via Solr admin UI or create it manually from CLI with additional parameters:

Wodby environment

  • Go to Instance > Stack > Search Engine page
  • Copy and execute Access container on your host server to access the container with Solr
  • Copy Create Solr core command (edit to change core name), execute it inside of the container

Local environment

  1. Access a running Solr container
  2. Create a core
    make create core=[core name] -f /usr/local/bin/actions.mk
    

Reloading solr core

You can reload the core from the Solr admin dashboard or by executing the following orchestration action from the container with running Solr:

make reload core=[core name] -f /usr/local/bin/actions.mk

Customizing solr core

By default we create cores with a reference to a config set, this means that a core does not have its own config but instead uses config files of pre-existing configuration. Available config sets listed under configsets/* in the default working directory. To learn which config set used in your core navigate to your core directory, it's a directory in the default working dir (/opt/solr/server/solr) that matches your core name. In this directory you'll find core.properties file that contains configSet= line where a currently used config set specified.

Now there two ways how you can customize your core config:

1. By creating new config set

Use this approach when you'll need to use your customized config for multiple cores.

  1. Access the container with running Solr
  2. Use existing config set as your boilerplate by copying a directory under configsets/*
  3. The name of directory under configsets/* will be the name of your config set
  4. Once the config set is ready update configSet= line in core.properties file inside your core directory
  5. Reload core

Do not modify predefined config set

Do not modify config sets that come with the image because all changes will be lost after a container restart.

2. By moving configuration to core

Use this approach when you'll need a unique configuration per core.

  1. Access the container with running Solr
  2. Use existing config set as your boilerplate by copying configsets/[CONFIG SET]/conf to [CORE NAME]/conf
  3. Once the config set is ready delete configSet= line in core.properties file inside your core directory
  4. Reload core

Changelog

This changelog is for Solr stack on Wodby, to see image changes see tags description on repository page

2.0.1

Solr patch update: 6.6.5

2.0.0

  • New Solr versions added: 7.4, 7.3
  • Dropped versions 6.3, 6.5, 7.0
  • Config sets and solr.xml now symlinked to volume, existing cores won't be affected
  • Core directory get deleted when you delete a core via orchestration actions
  • Bugfix: duplicated configsets/configsets directory

1.2.1

  • New 7.2 version added
  • Patch update: 6.6.3

1.2.0

1.1.0

  • New Solr versions 7.0.1 and 7.1.0 have been added
  • Solr versions updated and freezed: 6.6.2, 6.5.1, 6.4.2, 6.3.0, 5.5.5, 5.4.1
  • We now create a default solr core named default automatically if no cores found
  • Health check timeouts increased to 30 seconds

1.0.3

  • Solr: fixed persistent data paths configuration

1.0.1

1.0.0

Initial release