Using multiple search cores

Multiple Acquia Search cores

Acquia Search supports the use of separate search cores, both by Acquia Cloud environment or multisite instance. This allows each environment (Development, Staging, and Production) to have its own separate search core, enabling development and testing using independent Solr configuration and data.

Per-environment connection behavior

The Drupal modules for Acquia Search detect the current application's environment and then connect to the ideal Acquia-hosted Solr core. This default can be overridden.

As an example, if your current Acquia subscription (named in this example ABCD-12345) has three Solr cores:

  • ABCD-12345.dev.default (Development)
  • ABCD-12345.test.default (Staging)
  • ABCD-12345.prod.default (Production)

and you attempt to copy a website between environments, one of following actions will occur:

  • A valid core is found
    An Acquia-hosted website running in the development environment in the sites/default directory will use the ABCD-12345.dev.default core. If you then copy this website to the Acquia test environment, the Solr connection will switch to the ABCD-12345.test.default core.
  • No valid core is found
    If you do not have a valid Solr core defined for an environment, automatic switching will not take place, and the connection will switch to read-only mode on the production core. This protects your Solr data from being modified by other websites. Without this protection, several scenarios could result in data corruption/pollution, or even pose security issues (such as accidentally exposing privileged information on unwanted websites).
    As an example, if you copy your Acquia-hosted production website to an Acquia-hosted environment named QA and if there is no currently-defined QA Solr core in your subscription, the modules will connect in read-only mode to the production core at ABCD-12345.prod.default.
    When the Acquia Search modules enable read-only mode on a connection, your website can still run searches against an Acquia Search Solr core, even though operations that include changing, adding, or deleting content will not work. Without this protection, the website copy may delete or otherwise corrupt your production Solr core as you edit and delete content, run indexing, or run cron. Your visitors will begin to see nonsensical results on search pages on your production website, for which the only fix is to completely reindex Solr for the production website.

Reviewing the current Acquia Search connection status

To determine the current connection status of your website's connection, you can use the Drupal administrative interface and examine the Connection status dialog box.

As a Drupal administrator, use one of the following methods to determine the connection status:

  • Navigate to Reports > Status report for a summary of your connections.
  • Search API module - Navigate to Configuration > Search API, and then click each server name.
  • Apache Solr Search Integration module - Navigate to Configuration > Apache Solr search, and then click Edit for each displayed environment.

Additional troubleshooting may be required if there is a problem connecting to the core.

Drupal Projects

Contact supportStill need assistance? Contact Acquia Support