Acquia Search may experience downtime when servers are rebooted for security reasons.
Use the following steps when you troubleshoot issues with Acquia Search with the Apache Solr Search module:
/admin/settings/apachesolr/query-fields
to ensure no major fields are configured to Omit. Also, scroll to the bottom of /admin/settings/apachesolr/content-bias
and check which content types are excluded from indexing.Find the last node indexed by completing the following steps:
Run the following command:
drush -vd search-index
At some point, you’ll start seeing notices about what node IDs failed to index. Run the following command and note the limit:
drush vget apachesolr_cron_limit
Divide the number returned by the previous command by 2
, and then use the resulting number with the following command:
drush vset apachesolr_cron_limit [value]
For example, if you have 100 results, run the following command:
drush vset apachesolr_cron_limit 50
1
as the returned number.When you reach 1
, you will know which node is causing problems.
Another technique to find the last indexed node is to use the following command:
drush vget apachesolr_index_last
Use the following command for Drupal 7:
drush php-eval 'module_load_include("inc", "apachesolr", "apachesolr.index"); $rows = apachesolr_index_get_entities_to_index(apachesolr_default_environment(), "node", 1); foreach ($rows as $row) { print_r($row); }'
The reported node is probably where the indexing problem resides.
If this content did not answer your questions, try searching or contacting our support team for further assistance.
Wed May 28 2025 08:44:36 GMT+0000 (Coordinated Universal Time)