Cloud Platform
Configuring flood controls with the Acquia Search powered by SearchStax Drupal module
Flood controls, also known as rate limiting, restrict the number of search requests sent in a specific time period. Flood limits use a sliding time window and a maximum request count:
When requests exceed the configured limit during the active window, Drupal suppresses additional requests until traffic falls below the threshold, this functionality is based on the Drupal core Flood API.
Rate limiting prevents automated tools or misconfigured code from overwhelming the system with excessive queries. This approach ensures that you stay within SearchStax subscription limits and preserve peak search performance for users. These controls replicate the specific flood control protections as originally provided by Acquia Search to maintain a stable and secure environment (glossary term, activate to view definition).
Before you enable flood controls, ensure that:
Back up the codebase and configuration.
Update the module through Composer:
composer require drupal/searchstax:^1.10
Run the database updates:
drush updb
Clear the cache:
drush cr
Ensure that the SearchStax module version is 1.10.0 or later.
Log in to the Drupal site as an administrator (glossary term, activate to view definition) account.
Navigate to the SearchStax module configuration page (/admin/config/search/searchstax).
Locate the Flood Protection section.
Select Enable Flood Protection.
Set the limits for Search Window, Search Limit, Update Window, and Update Limit.
Save the changes.
Ensure that you monitor search behavior and logs to adjust limits as needed.
For additional information, visit Configure Flood Limits in the Drupal Module.
After a user exceeds flood limits, the module responds in the following manner:
The module code emits the SearchStax flood protection: <type> limit reached.error message. In this message, the type is either Search or Update.
The module logs an entry that includes the user identifier and the exceeded limit.
Follow these best practices to manage users:
Cloud Platformsettings.php overrides to set different flood limits for development, staging, and production environments.If this content did not answer your questions, try searching or contacting our support team for further assistance.
Flood controls, also known as rate limiting, restrict the number of search requests sent in a specific time period. Flood limits use a sliding time window and a maximum request count:
When requests exceed the configured limit during the active window, Drupal suppresses additional requests until traffic falls below the threshold, this functionality is based on the Drupal core Flood API.
Rate limiting prevents automated tools or misconfigured code from overwhelming the system with excessive queries. This approach ensures that you stay within SearchStax subscription limits and preserve peak search performance for users. These controls replicate the specific flood control protections as originally provided by Acquia Search to maintain a stable and secure environment (glossary term, activate to view definition).
Before you enable flood controls, ensure that:
Back up the codebase and configuration.
Update the module through Composer:
composer require drupal/searchstax:^1.10
Run the database updates:
drush updb
Clear the cache:
drush cr
Ensure that the SearchStax module version is 1.10.0 or later.
Log in to the Drupal site as an administrator (glossary term, activate to view definition) account.
Navigate to the SearchStax module configuration page (/admin/config/search/searchstax).
Locate the Flood Protection section.
Select Enable Flood Protection.
Set the limits for Search Window, Search Limit, Update Window, and Update Limit.
Save the changes.
Ensure that you monitor search behavior and logs to adjust limits as needed.
For additional information, visit Configure Flood Limits in the Drupal Module.
After a user exceeds flood limits, the module responds in the following manner:
The module code emits the SearchStax flood protection: <type> limit reached.error message. In this message, the type is either Search or Update.
The module logs an entry that includes the user identifier and the exceeded limit.
Follow these best practices to manage users:
settings.php overrides to set different flood limits for development, staging, and production environments.If this content did not answer your questions, try searching or contacting our support team for further assistance.