Subscribers with websites using the Acquia Search platform have limits for some or all of the following resources: total queries, documents, and disk space. If these limits are consistently met or exceeded, Acquia reserves the right to restrict the website’s use of the shared search resources or move your website to a dedicated Acquia Search instance at your expense.
Acquia will not generally block access to your Solr index. However, a block could occur in an emergency where your or another customer’s data or service could be impacted.
If you are not yet at your limit, you can proactively take steps to prevent your website from ever reaching them. Here are some factors to consider as you plan for usage:
If you are concerned you may exceed your limits, your next step is to contact Acquia support, or your account manager to get help determining the best fit for your website.
If you have exceeded your subscription limits, here are some of the possible actions Acquia may take:
Acquia Search uses three metrics for your subscription: disk storage size, number of Solr requests from Drupal, and the number of documents in the index. You can use different strategies to reduce usage in one or more of these areas.
All of your Acquia subscription’s Solr indexes (production and non-production) count toward your limits. Reduce usage of some or all non-production indexes, or remove indexes entirely to stay within your subscription bounds.
Several issues can trigger a high number of requests to your Acquia Search Solr back end:
| Situation | Action |
|---|---|
| Autocomplete widgets powered by Solr |
|
| Usage of More Like This content recommendation blocks | Cache these blocks or reduce their usage. |
| Elevated traffic that triggers Solr queries | Often caused by crawlers following links that trigger Solr requests.
|
| The Index immediately option is enabled in Search API. | Compounded by mass importing or editing of content.
|
| The Search 404 module is enabled. | Made worse by crawlers and traffic.
|
| Mass content edits, imports or migrations | Disable indexing while doing any mass content handling. |
| Out of date modules | Ensure your modules are up to date. |
If you’re using Drupal 7, one way to understand what data is being sent to your Solr index is to use the Solr Devel module, which adds a Devel > Solr tab on each entity. This enables you to see what’s already in your Solr index and what data would be sent if you were to index an item.
If you aren’t careful about what you are indexing, the size of your Solr index can increase rapidly, consuming excessive disk space. There are several potential causes:
| Situation | Action |
|---|---|
Automated Solr optimize isn’t running |
The Optimize Solr operation is usually invoked weekly by Drupal modules and is responsible for reclaiming disk space after deletes and garbage collection.
|
| Indexing too many fields or entity data | This often occurs when indexing nodes with many comments.
|
| Indexing large attachments with large amounts of text | Large PDF or text files can fill disk space quickly.
|
The relationship between the number of Drupal entities and number of Solr documents is not always one-to-one; Drupal can process a single entity such as a node or a user into multiple Solr documents. For example:
node/1 has three attached files. This can create four Solr documents;
one for the node, and one for each attachment.node/1 has field data in three languages. This may create four Solr
documents; one for each language.To reduce the number of documents in your Solr index:
53 State Street, 10th Floor
Boston, MA 02109
United States
Phone: 888-922-7842