Lock wait timeout exceeded

samspinoy created an issue. See original summary.

Yeah I only track entities that need to be tracked. But I have 6000+ nodes and since tracking revisions cannot be turned off, it's still huge.

I take it there is no way to not track revisions?

But what does that scenario have to do with this module? You mean the tracking would be wrong, making users think there are no more usages for node B?

While I see your point, most of the editors on this project don't bother checking revisions and doing rollbacks. Also if it can shrink my db table by 90%, it's worth the risk.

So how could I go about updating a usage record each time an entity gets saved, rather than adding a new one for each revision? Is this logic in a plugin that can be overwritten?

I have actually managed to get this to work with the implementation of the following two hooks:

/**
 * Implements hook_entity_presave().
 *
 * Delete all tracking with this entity as target. This is to keep clean records,
 * otherwise deleted values from fields will not be purged.
 */
function mymodule_entity_presave(EntityInterface $entity) {
  \Drupal::database()
    ->delete('entity_usage')
    ->condition('source_id', $entity->id())
    ->condition('source_type', $entity->getEntityTypeId())
    ->execute();
}

/**
 * Implements hook_entity_usage_block_tracking().
 *
 * Block all tracking coming from the module and keep our own (only one) record.
 * Main reason for this is that we do not want to track revisions.
 */
function mymodule_entity_usage_block_tracking($target_id, $target_type, $source_id, $source_type, $source_langcode, $source_vid, $method, $field_name, $count) {
  if ($count > 0) {
    \Drupal::database()
      ->merge('entity_usage')
      ->key([
        'target_id' => $target_id,
        'target_type' => $target_type,
        'source_id' => $source_id,
        'source_type' => $source_type,
        'source_langcode' => $source_langcode,
        'source_vid' => 0,
        'method' => $method,
        'field_name' => $field_name,
        'count' => $count,
      ])
      ->execute();
  }

  return TRUE;
}

This only keeps one record per entity and keeps records nicely up to date with update/delete. You probably think I am butchering your module :) but this works for my use-case.