Search in book...
Toggle Font Controls
Create new playlist

Name your new playlist

Playlist description (optional)
Sign In

Email address

Password

Forgot Password?

or

Continue with Facebook

Continue with Google
Sign Up

Full Name

Email address

Confirm Email Address

Password

or

Continue with Facebook

Continue with Google

Core Admin

The Core Admin section is a central point where you can manage registered cores. You can create a new core on-the-fly (assuming that the core instance and data directories exist on the disk) or manage the existing cores one by one, selecting them from the list on the left. The following screenshot shows the Core Admin page of the Solr instance set up for this chapter:

The top toolbar contains these buttons:

Button	Description
Unload	Unloads the core. The core will be removed after pending requests are processed.
Rename	Changes the core name. Note that this change will affect the URI endpoints of the core services.
Swap	Swaps two active cores. This is useful for switching between two versions (that is, online and offline versions) of the same core. Note that both of them will still be alive after issuing the swap command.
Reload	Reloads a core. The current core instance will be available only for satisfying pending requests. This command is useful if some (backward-compatible) changes have been made to the `solrconfig.xml` or `schema.xml` configuration files or core libraries and you want to load those changes.
Optimize	Issues an optimize command to the selected core.

The central area shows the following information about the core and the corresponding index:

Attribute	Description
startTime	The core start (or reload) time.
instanceDir	The top core folder. It contains a `conf` subfolder that contains Solr configuration files (`schema.xml`, `solrconfig.xml`, and dependent files).
dataDir	The folder containing the index data files.
lastModified	The last modification date of the index.
version	A version number assigned to the IndexReader instance associated with the index.
numDocs	The number of searchable documents in the index. In other words, this is the number of documents you can get back from a `:` query.
maxDocs	The number of internal document identifiers actually in use. The difference between `maxDocs` and `numDocs` indicates how many documents have been deleted or replaced. The old (deleted and replaced) identifiers are gradually removed during merges or after issuing an index optimize.
deletedDocs	The number of deleted documents. It also includes replaced documents because Solr doesn't actually support updates; it simply deletes a given document and subsequently adds its new version. This is basically the difference between `maxDocs` and `numDocs` after a commit and before merging or optimizing.
optimized	Indicates whether the index has been optimized.
current	Indicates whether the index has been committed.
directory	The underlying Lucene Directory implementation.

..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.

Table of Contents for Core Admin

Create new playlist

Sign In

Sign Up

Core Admin

Table of Contents for
Core Admin