Performing a full reindex with Solr

This task assumes you are using only one Solr instance for all nodes in the Alfresco Content Services cluster. If not, then you
need to repeat process on each Solr instance used in the cluster.

Confirm the location of the Solr core directories for
archive-SpacesStore and workspace-SpacesStore
cores. This can be determined from the solrcore.properties file for
both the cores. By default, the solrcore.propertiesfile can be found
at <ALFRESCO_HOME>/solr4/workspace-SpacesStore/conf or
<ALFRESCO_HOME>/solr4/archive-SpacesStore/conf. The Solr core
location is defined in the solrcore.properties file as:

For Solr, the default data.dir.root path
is:

data.dir.root=<ALFRESCO_HOME>/alf_data/solr4/index/

Shut down Solr (if running on a separate application server).

Delete the contents of the index data directories for each Solr core at
${data.dir.root}/${data.dir.store}.

<ALFRESCO_HOME>/alf_data/solr4/index/workspace/SpacesStore

<ALFRESCO_HOME>/alf_data/solr4/index/archive/SpacesStore

Delete all the Alfresco Content Services
models for each Solr core at ${data.dir.root}.

<ALFRESCO_HOME>/alf_data/solr4/model

Delete the contents of the
<ALFRESCO_HOME>/alf_data/solr4/content directory.

Start up the application server that runs Solr.

Monitor the application server logs for Solr at
<TOMCAT_HOME>/logs/solr.log. You will get the following warning
messages on bootstrap:

Use the Solr administration console to check the health of the Solr index.

Note: The process of building the Solr indexes can take some time depending on the size
of the repository. To monitor reindexing progress, use the Solr administration console
and check the logs for any issues during this activity.

While the reindex is taking
place, some searches may not return the full set of results.

To copy the indexes from a recently re-indexed Solr node to another Solr node, follow
these steps:

Make sure both the Solr nodes have the same version of the index server.

Stop node1 and copy the content store, index configuration, and index data to the new
machine/node.

(Optional) Copy the models from node1 to node2 and validate that they are
compatible.

Fix any configuration issues, for example, renaming the core, updating the configuration
to point to the correct data, indexes, and Alfresco Content Services.

Disable index tracking on node2 by setting the enable.alfresco.tracking
property to false in solrcore.properties.

Go to the Solr Admin Web interface to monitor information about each core.

Stop node 2 and enable tracking by setting the enable.alfresco.tracking
property to true in solrcore.properties.

You don't appear to have JavaScript enabled in your browser. With
JavaScript enabled, you can provide feedback to us using our simple form.
Here are some instructions
on how to enable JavaScript in your web browser.