Apache Solr Reference Guide Covering Apache Solr 6.0

schema 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 details.
dataDir
configSet
properties
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 Config
Sets 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.
transient 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 to t
rue is not recommended in SolrCloud mode.
loadOnStartup If true, the default if it is not specified, the core will loaded when Solr starts. Setting to fals
e is not recommended in SolrCloud mode.
coreNodeName 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:
when replacing a machine that has had a hardware failure by restoring from backups on a
new machine with a new hostname or port..
ulogDir
shard
collection
roles
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 param 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.
CoreAdmin API
The Core Admin API is primarily used under the covers by the Collections API when running a SolrCloud cluster.
SolrCloud users should not typically use the CoreAdmin API directly – but it may be useful for users of
single-node or master/slave Solr installations for core maintenance operations.
The CoreAdmin API is implemented by the CoreAdminHandler, which is a special purpose SolrRequestHandler
that is used to manage Solr cores. Unlike normal SolrRequestHandlers, the CoreAdminHandler is not attached to
a single core. Instead, it there is a single instance of the CoreAdminHandler in each Solr node that manages all
the cores running in that node and is accessible at the /solr/admin/cores path.
CoreAdmin actions can be executed by via HTTP requests that specify an " action" request parameter, with
additional action specific arguments provided as additional parameters.
All action names are uppercase, and are defined in depth in the sections below.
STATUS
Apache Solr Reference Guide 6.0
472