Solr (Search service)

Apache Solr is a scalable and fault-tolerant search index.

Solr search with generic schemas provided, and a custom schema is also supported. See the Solr documentation for more information.

Supported versions

You can select the major and minor version.

Patch versions are applied periodically for bug fixes and the like. When you deploy your app, you always get the latest available patches.

• 9.6
• 9.4
• 9.2
• 9.1
• 8.11

Deprecated versions

The following versions are deprecated. They’re available, but they aren’t receiving security updates from upstream and aren’t guaranteed to work. They’ll be removed in the future, so migrate to one of the supported versions.

• 8.6
• 8.4
• 8.0
• 7.7
• 7.6
• 6.6
• 6.3
• 4.10
• 3.6

Relationship reference

For each service defined via a relationship to your application, Upsun automatically generates corresponding environment variables within your application container, in the $<RELATIONSHIP-NAME>_<SERVICE-PROPERTY> format.

Here is example information available through the service environment variables themselves, or through the PLATFORM_RELATIONSHIPS environment variable.

SOLR_USERNAME=
SOLR_SCHEME=solr
SOLR_SERVICE=solr
SOLR_IP=123.456.78.90
SOLR_FRAGMENT=
SOLR_HOSTNAME=azertyuiopqsdfghjklm.solr.service._.eu-1.platformsh.site
SOLR_PORT=8080
SOLR_CLUSTER=azertyuiopqsdf-main-afdwftq
SOLR_HOST=solr.internal
SOLR_REL=solr
SOLR_PATH=solr/collection1
SOLR_QUERY={}
SOLR_PASSWORD=
SOLR_EPOCH=0
SOLR_TYPE=solr:9.6
SOLR_PUBLIC=false
SOLR_HOST_MAPPED=false

{
    "username": null,
    "scheme": "solr",
    "service": "solr",
    "fragment": null,
    "ip": "123.456.78.90",
    "hostname": "azertyuiopqsdfghjklm.solr.service._.eu-1.platformsh.site",
    "port": 8080,
    "cluster": "azertyuiopqsdf-main-afdwftq",
    "host": "solr.internal",
    "rel": "solr",
    "path": "solr\/collection1",
    "query": [],
    "password": null,
    "type": "solr:9.6",
    "public": false,
    "host_mapped": false
}

# Decode the built-in credentials object variable.
export RELATIONSHIPS_JSON=$(echo $PLATFORM_RELATIONSHIPS | base64 --decode)

# Set environment variables for individual credentials.
export APP_SOLR_HOST="$(echo $RELATIONSHIPS_JSON | jq -r '.solr[0].host')"

Usage example

1. Configure the service

To define the service, use the solr type:

services:
    # The name of the service container. Must be unique within a project.
    <SERVICE_NAME>:
        type: solr:<VERSION>

Note that changing the name of the service replaces it with a brand new service and all existing data is lost. Back up your data before changing the service.

2. Add the relationship

To define the relationship, use the following configuration:

applications:
    # The name of the app container. Must be unique within a project.
    <APP_NAME>:
        # Relationships enable access from this app to a given service.
        # The example below shows simplified configuration leveraging a default service
        # (identified from the relationship name) and a default endpoint.
        # See the Application reference for all options for defining relationships and endpoints.
        relationships:
            <SERVICE_NAME>: 
services:
    # The name of the service container. Must be unique within a project.
    <SERVICE_NAME>:
        type: solr:<VERSION>

You can define <SERVICE_NAME> as you like, so long as it’s unique between all defined services and matches in both the application and services configuration.

The example above leverages default endpoint configuration for relationships. That is, it uses default endpoints behind-the-scenes, providing a relationship (the network address a service is accessible from) that is identical to the name of that service.

Depending on your needs, instead of default endpoint configuration, you can use explicit endpoint configuration.

With the above definition, the application container (<APP_NAME>) now has access to the service via the relationship <RELATIONSHIP_NAME> and its corresponding service environment variables.

Example configuration

applications:
    # The name of the app container. Must be unique within a project.
    myapp:
        # Relationships enable access from this app to a given service.
        # The example below shows simplified configuration leveraging a default service
        # (identified from the relationship name) and a default endpoint.
        # See the Application reference for all options for defining relationships and endpoints.
        relationships:
            solr: 

services:
    # The name of the service container. Must be unique within a project.
    solr:
        type: solr:9.6

Use in app

To use the configured service in your app, add a configuration file similar to the following to your project.

applications:
    # The name of the app container. Must be unique within a project.
    myapp:
        # The location of the application's code.
        source:
            root: "myapp"

        [...]

        # Relationships enable an app container's access to a service.
        relationships:
            solr:

services:
    # The name of the service container. Must be unique within a project.
    solr:
        type: solr:9.6

This configuration defines a single application (myapp), whose source code exists in the <PROJECT_ROOT>/myapp directory.
myapp has access to the solr service, via a relationship whose name is identical to the service name (as per default endpoint configuration for relationships).

From this, myapp can retrieve access credentials to the service through the relationship environment variables.

# Set environment variables for individual credentials.
# For more information, please visit https://docs.upsun.com/development/variables.html#service-environment-variables.
export QUEUE_SCHEME=${RABBITMQ_SCHEME}
export QUEUE_USERNAME=${RABBITMQ_USERNAME}
export QUEUE_PASSWORD=${RABBITMQ_PASSWORD}
export QUEUE_HOST=${RABBITMQ_HOST}
export QUEUE_PORT=${RABBITMQ_PORT}

# Set a single RabbitMQ connection string variable for AMQP.
export AMQP_URL="${QUEUE_SCHEME}://${QUEUE_USERNAME}:${QUEUE_PASSWORD}@${QUEUE_HOST}:${QUEUE_PORT}/"

The above file — .environment in the myapp directory — is automatically sourced by Upsun into the runtime environment, so that the variable SEARCH_URL can be used within the application to connect to the service.

Note that SEARCH_URL, and all Upsun service environment variables like SOLR_HOST, are environment-dependent. Unlike the build produced for a given commit, they can’t be reused across environments and only allow your app to connect to a single service instance on a single environment.

A file very similar to this is generated automatically for your when using the upsun ify command to migrate a codebase to Upsun.

Solr 4

For Solr 4, Upsun supports only a single core per server called collection1.

You must provide your own Solr configuration via a core_config key in your .upsun/config.yaml:

services:
    # The name of the service container. Must be unique within a project.
    solr:
        type: "solr:4.10"
        configuration:
            core_config: !archive "DIRECTORY"

DIRECTORY points to a directory in the Git repository, in or below the .upsun/ folder. This directory needs to contain everything that Solr needs to start a core. At the minimum, solrconfig.xml and schema.xml.

For example, place them in .upsun/solr/conf/ such that the schema.xml file is located at .upsun/solr/conf/schema.xml. You can then reference that path like this -

services:
    # The name of the service container. Must be unique within a project.
    solr:
        type: "solr:4.10"
        configuration:
            core_config: !archive "solr/conf/"

Solr 6 and later

For Solr 6 and later Upsun supports multiple cores via different endpoints. Cores and endpoints are defined separately, with endpoints referencing cores. Each core may have its own configuration or share a configuration. It is best illustrated with an example.

services:
    # The name of the service container. Must be unique within a project.
    solr:
        type: solr:9.6
        configuration:
            cores:
                mainindex:
                    conf_dir: !archive "core1-conf"
                extraindex:
                    conf_dir: !archive "core2-conf"
            endpoints:
                main:
                    core: mainindex
                extra:
                    core: extraindex

The above definition defines a single Solr 9.6 server. That server has 2 cores defined:

• mainindex — the configuration for which is in the .upsun/core1-conf directory
• extraindex — the configuration for which is in the .upsun/core2-conf directory.

It then defines two endpoints: main is connected to the mainindex core while extra is connected to the extraindex core. Two endpoints may be connected to the same core but at this time there would be no reason to do so. Additional options may be defined in the future.

Each endpoint is then available in the relationships definition in .upsun/config.yaml. For example, to allow an application to talk to both of the cores defined above its configuration should contain the following:

applications:
    # The name of the app container. Must be unique within a project.
    myapp:
    
        type: "php:8.3"

        source:
            root: "myapp"

        [...]

        relationships:
            solrsearch1: 
                service: solr
                endpoint: main
            solrsearch2:
                service: solr
                endpoint: extra

services:
    # The name of the service container. Must be unique within a project.
    solr:
        type: solr:9.6
        configuration:
            cores:
                mainindex:
                    conf_dir: !archive "core1-conf"
                extraindex:
                    conf_dir: !archive "core2-conf"
            endpoints:
                main:
                    core: mainindex
                extra:
                    core: extraindex

That is, the application’s environment would include a solrsearch1 relationship that connects to the main endpoint, which is the mainindex core, and a solrsearch2 relationship that connects to the extra endpoint, which is the extraindex core.

The relationships array would then look something like the following:

{
    "solrsearch1": [
        {
            "path": "solr/mainindex",
            "host": "248.0.65.197",
            "scheme": "solr",
            "port": 8080
        }
    ],
    "solrsearch2": [
        {
            "path": "solr/extraindex",
            "host": "248.0.65.197",
            "scheme": "solr",
            "port": 8080
        }
    ]
}

Configsets

For even more customizability, it’s also possible to define Solr configsets. For example, the following snippet would define one configset, which would be used by all cores. Specific details can then be overridden by individual cores using core_properties, which is equivalent to the Solr core.properties file.

services:
    # The name of the service container. Must be unique within a project.
    solr:
        type: solr:9.6
        configuration:
            configsets:
                mainconfig: !archive "configsets/solr8"
            cores:
                english_index:
                    core_properties: |
                        configSet=mainconfig
                        schema=english/schema.xml                        
                arabic_index:
                    core_properties: |
                        configSet=mainconfig
                        schema=arabic/schema.xml                        
            endpoints:
                english:
                    core: english_index
                arabic:
                    core: arabic_index

In this example, .upsun/configsets/solr8 contains the configuration definition for multiple cores. There are then two cores created:

• english_index uses the defined configset, but specifically the .upsun/configsets/solr8/english/schema.xml file
• arabic_index is identical except for using the .upsun/configsets/solr8/arabic/schema.xml file.

Each of those cores is then exposed as its own endpoint.

Note that not all core properties features make sense to specify in the core_properties. Some keys, such as name and dataDir, aren’t supported, and may result in a solrconfig that fails to work as intended, or at all.

Default configuration

Default for version 9+

If you don’t specify any configuration, the following default is used:

services:
    # The name of the service container. Must be unique within a project.
    solr:
        type: solr:9.6
        configuration:
            cores:
                collection1:
                    conf_dir: !archive "example"
            endpoints:
                solr:
                    core: collection1

The example configuration directory is equivalent to the Solr example configuration set. This default configuration is designed only for testing. You are strongly recommended to define your own configuration with a custom core and endpoint.

Default for versions below 9

If you don’t specify any configuration, the following default is used:

services:
    # The name of the service container. Must be unique within a project.
    solr:
        type: solr:8.4
        configuration:
            cores:
                collection1: {}
            endpoints:
                solr:
                    core: collection1

The default configuration is based on an older version of the Drupal 8 Search API Solr module that is no longer in use. You are strongly recommended to define your own configuration with a custom core and endpoint.

Limitations

The recommended maximum size for configuration directories (zipped) is 2MB. These need to be monitored to ensure they don’t grow beyond that. If the zipped configuration directories grow beyond this, performance declines and deploys become longer. The directory archives are compressed and string encoded. You could use this bash pipeline

echo $(($(tar czf - . | base64 | wc -c )/(1024*1024))) Megabytes

inside the directory to get an idea of the archive size.

The configuration directory is a collection of configuration data, like a data dictionary, e.g. small collections of key/value sets. The best way to keep the size small is to restrict the directory context to plain configurations. Including binary data like plugin .jar files inflates the archive size, and isn’t recommended.

Accessing the Solr server administrative interface

Because Solr uses HTTP for both its API and admin interface it’s possible to access the admin interface over an SSH tunnel.

upsun tunnel:single --relationship RELATIONSHIP_NAME

By default, this opens a tunnel at 127.0.0.1:30000.

You can now open http://localhost:30000/solr/ in a browser to access the Solr admin interface. Note that you can’t create indexes or users this way, but you can browse the existing indexes and manipulate the stored data.

Available plugins

This is the complete list of plugins that are available and loaded by default:

Upgrading

The Solr data format sometimes changes between versions in incompatible ways. Solr doesn’t include a data upgrade mechanism as it is expected that all indexes can be regenerated from stable data if needed. To upgrade (or downgrade) Solr you need to use a new service from scratch.

There are two ways of doing that.

Destructive

In your .upsun/config.yaml file, change the version of your Solr service and its name. Be sure to also update the reference to the now changed service name in it’s corresponding application’s relationship block.

When you push that to Upsun, the old service is deleted and a new one with the name is created, with no data. You can then have your application re-index data as appropriate.

This approach has the downside of temporarily having an empty Solr instance, which your application may or may not handle gracefully, and needing to rebuild your index afterward. Depending on the size of your data that could take a while.

Transitional

For a transitional approach you temporarily have two Solr services. Add a second Solr service with the new version a new name and give it a new relationship in .upsun/config.yaml. You can optionally run in that configuration for a while to allow your application to populate indexes in the new service as well.

Once you’re ready to cut over, remove the old Solr service and relationship. You may optionally have the new Solr service use the old relationship name if that’s easier for your application to handle. Your application is now using the new Solr service.

This approach has the benefit of never being without a working Solr instance. On the downside, it requires two running Solr servers temporarily, each of which consumes resources and need adequate disk space. Depending on the size of your data that may be a lot of disk space.