Configuring flood controls with the Acquia Search powered by SearchStax Drupal module
SearchStax Drupal module version 1.10.0 and later includes optional flood controls that mimic the query rate limiting previously available with Acquia Search. Flood controls protect the SearchStax-backed search index from excessive or abusive requests that can impact performance or exceed subscription limits.
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:
Window: The number of seconds Drupal checks.
Limit: The maximum number of requests Drupal permits during that window.
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.
Document existing limits: Review historic behavior and limits from Acquia Search.
Implement comparable limits: Use SearchStax settings to approximate previous limits.
Test user journeys: Ensure that normal search, autocomplete, and faceting do not trigger rate limits for typical users.
Monitor post-launch: Check logs and analytics after migration to determine if limits are appropriate.
Configuring flood controls with the Acquia Search powered by SearchStax Drupal module
SearchStax Drupal module version 1.10.0 and later includes optional flood controls that mimic the query rate limiting previously available with Acquia Search. Flood controls protect the SearchStax-backed search index from excessive or abusive requests that can impact performance or exceed subscription limits.
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:
Window: The number of seconds Drupal checks.
Limit: The maximum number of requests Drupal permits during that window.
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.