Configuring solrconfig.xml

The solrconfig.xml file is the configuration file with the most parameters affecting Solr itself.

While configuring Solr, you’ll work with solrconfig.xml often, either directly or via the Config API to create "configuration overlays" (configoverlay.json) to override the values in solrconfig.xml.

In solrconfig.xml, you configure important features such as:

  • request handlers, which process the requests to Solr, such as requests to add documents to the index or requests to return results for a query

  • listeners, processes that "listen" for particular query-related events; listeners can be used to trigger the execution of special code, such as invoking some common queries to warm-up caches

  • the Request Dispatcher for managing HTTP communications

  • the Admin Web interface

  • parameters related to replication and duplication (these parameters are covered in detail in Legacy Scaling and Distribution)

The solrconfig.xml file is located in the conf/ directory for each collection. Several well-commented example files can be found in the server/solr/configsets/ directories demonstrating best practices for many different types of installations.

We’ve covered the options in the following sections:

Substituting Properties in Solr Config Files

Solr supports variable substitution of property values in config files, which allows runtime specification of various configuration options in solrconfig.xml. The syntax is ${propertyname[:option default value]}. This allows defining a default that can be overridden when Solr is launched. If a default value is not specified, then the property must be specified at runtime or the configuration file will generate an error when parsed.

There are multiple methods for specifying properties that can be used in configuration files. Of those below, strongly consider "config overlay" as the preferred approach, as it stays local to the config set and because it’s easy to modify.

JVM System Properties

Any JVM System properties, usually specified using the -D flag when starting the JVM, can be used as variables in any XML configuration file in Solr.

For example, in the sample solrconfig.xml files, you will see this value which defines the locking type to use:


Which means the lock type defaults to "native" but when starting Solr, you could override this using a JVM system property by launching the Solr it with:

bin/solr start -Dsolr.lock.type=none

In general, any Java system property that you want to set can be passed through the bin/solr script using the standard -Dproperty=value syntax. Alternatively, you can add common system properties to the SOLR_OPTS environment variable defined in the Solr include file (bin/ or bin/ For more information about how the Solr include file works, refer to: Taking Solr to Production.

Config API to Override solrconfig.xml

The Config API allows you to use an API to modify Solr’s configuration, specifically user defined properties. Changes made with this API are stored in a file named configoverlay.json. This file should only be edited with the API, but will look like this example:

{"userProps": {
    "dih.db.url": "jdbc:oracle:thin:@localhost:1521",
    "dih.db.user": "username",
    "dih.db.pass": "password"}}

For more details, see the section Config API.

If the configuration directory for a Solr core contains a file named that file can contain any arbitrary user-defined property names and values using the Java properties file format. Those properties can then be used as variables in other configuration files for that Solr core.

For example, the following file could be created in the conf/ directory of a collection using one of the example configurations, to override the lockType used.

Deprecation won’t work in SolrCloud mode (it is not read from ZooKeeper). This feature is likely to be removed in the future. Instead, use another mechanism like a config overlay.

The path and name of the file can be overridden using the properties property in

User-Defined Properties in

Every Solr core has a file, automatically created when using the APIs. When you create a SolrCloud collection, you can pass through custom parameters by prefixing the parameter name with as a parameter.

For example, to add a property named "my.custom.prop":




curl -X POST -H 'Content-type: application/json' -d '{"create": {"name": "gettingstarted", "numShards": "1", "": "edismax"}}' http://localhost:8983/api/collections

This will create a file that has at least the following properties (others omitted for brevity):

The my.custom.prop property can then be used as a variable, such as in solrconfig.xml:

<requestHandler name="/select">
  <lst name="defaults">
    <str name="defType">${my.custom.prop}</str>

Implicit Core Properties

Several attributes of a Solr core are available as "implicit" properties that can be used in variable substitution, independent of where or how the underlying value is initialized.

For example, regardless of whether the name for a particular Solr core is explicitly configured in or inferred from the name of the instance directory, the implicit property is available for use as a variable in that core’s configuration file:

<requestHandler name="/select">
  <lst name="defaults">
    <str name="collection_name">${}</str>

All implicit properties use the solr.core. name prefix, and reflect the runtime value of the equivalent property:


  • solr.core.config

  • solr.core.schema

  • solr.core.dataDir

  • solr.core.transient

  • solr.core.loadOnStartup