Setting limits for export¶

When preparing to publish content, Acquia Content Hub reviews both the number of nodes and how many levels of referenced content to send. This content is then processed, and any remaining content moves to the queue. Variable names are dependent on your Drupal version, and are described as follows:

• Current Drupal version: The current Drupal version has a single parameter to limit exported dependencies. The dependency_depth parameter limits the level of dependencies to evaluate, but doesn’t limit the actual number of exported items. This parameter can be also set by using Drush.

  drush config-set acquia_contenthub.entity_config dependency_depth 3
  

  This example sets the value to 3 (which is the default), and indicates that exporting collects entities on the first three level of dependencies.

• Drupal 7: The following variables can be set for export:

  • Depth - content_hub_connector_max_dep_depth
  • Load - content_hub_connector_max_dep_load
  • Send - content_hub_connector_max_dep_send
  • cache_exported - FALSE - When TRUE, this tracks which items that have changed, and doesn’t send unchanged items. This feature is still under development.

  Based on the default values for these variables, Acquia Content Hub will initially evaluate up to 30 levels of dependent content, and then load and send up to 500 items to the service.

  If Acquia Content Hub reaches its send limits, the following warning message displays:

  Content dependency limits were reached. Not all dependencies were
  submitted to Content Hub.
  

  A message also records in the status report (Reports > Status report), from content_hub_connector, which states how many items Acquia Content Hub sent to the queue, and will look like the following message:

  entity limit enforced: X not charted, Y not loaded, Z not sent
  

  where X, Y, and Z are the number of items not processed. The queue will process during standard Drupal cron runs.

Setting limits for import¶

When importing content from Acquia Content Hub, the amount of discovered and imported content also faces limitations based on dependency levels.

Variable names on the subscribing website:

• Load - content_hub_connector_max_entities_webhook_request
• Depth - content_hub_connector_max_dep_depth_import - limits the levels of dependent content to import
• Send/Receive - content_hub_connector_max_dep_receive

You can use Drush to check the import queue variable values and status, which returns the following items and their current values:

• Load - max dependencies
• Depth - max dependency gap
• Send/Receive - max items

Changing the queue processing class¶

When using queues for Acquia Content Hub, it’s good practice to switch the default queue processing class from DatabaseQueue to MemoryLimitDatabaseQueue, which the module provides. This class provides a graceful process termination when facing issues related to memory exhaustion.

To switch the default queue processing class, add the following lines to the website’s settings.php file after the Acquia require line:

$settings['queue_service_acquia_contenthub_export_queue'] = 'acquia_contenthub.queue.database.memory_limit';
$settings['queue_service_acquia_contenthub_import_queue'] = 'acquia_contenthub.queue.database.memory_limit';