Core discovery means that creating a core is as simple as a file located on disk.

The file is a simple Java Properties file where each line is just a key=value pair, e.g., name=core1. Notice that no quotes are required.

A minimal file looks like the example below. However, it can also be empty, see information on placement of below.


Placement of

Solr cores are configured by placing a file named in a sub-directory under solr.home. There are no a-priori limits to the depth of the tree, nor are there limits to the number of cores that can be defined. Cores may be anywhere in the tree with the exception that cores may not be defined under an existing core. That is, the following is not allowed:


In this example, the enumeration will stop at "core1".

The following is legal:


It is possible to segment Solr into multiple cores, each with its own configuration and indices. Cores may be dedicated to a single application or to very different ones, but all are administered through a common administration interface. You can create new Solr cores on the fly, shutdown cores, even replace one running core with another, all without ever stopping or restarting Solr.

Your file can be empty if necessary. Suppose is located in ./cores/core1 (relative to solr_home) but is empty. In this case, the core name is assumed to be "core1". The instanceDir will be the folder containing (i.e., ./cores/core1). The dataDir will be ../cores/core1/data, etc.

You can run Solr without configuring any cores.

Defining Files

The minimal file is an empty file, in which case all of the properties are defaulted appropriately.

Java properties files allow the hash (#) or bang (!) characters to specify comment-to-end-of-line.

The following properties are available:

The name of the SolrCore. You’ll use this name to reference the SolrCore when running commands with the CoreAdminHandler.
The configuration file name for a given core. The default is solrconfig.xml.
The schema file name for a given core. The default is schema.xml but please note that if you are using a "managed schema" (the default behavior) then any value for this property which does not match the effective managedSchemaResourceName will be read once, backed up, and converted for managed schema use. See Schema Factory Definition in SolrConfig for more details.
The core’s data directory (where indexes are stored) as either an absolute pathname, or a path relative to the value of instanceDir. This is data by default.
The name of a defined configset, if desired, to use to configure the core (see the section Configsets for more details).
The name of the properties file for this core. The value can be an absolute pathname or a path relative to the value of instanceDir.
If true, the core can be unloaded if Solr reaches the transientCacheSize. The default if not specified is false. Cores are unloaded in order of least recently used first. Setting this to true is not recommended in SolrCloud mode.
If true, the default if it is not specified, the core will loaded when Solr starts. Setting this to false is not recommended in SolrCloud mode.
Used only in SolrCloud, this is a unique identifier for the node hosting this replica. By default a coreNodeName is generated automatically, but setting this attribute explicitly allows you to manually assign a new core to replace an existing replica. For example, this can be useful when replacing a machine that has had a hardware failure by restoring from backups on a new machine with a new hostname or port.
The absolute or relative directory for the update log for this core (SolrCloud).
The shard to assign this core to (SolrCloud).
The name of the collection this core is part of (SolrCloud).
Future parameter for SolrCloud or a way for users to mark nodes for their own use.

Additional user-defined properties may be specified for use as variables. For more information on how to define local properties, see the section Substituting Properties in Solr Config Files.