Recibiendo errores de bloqueo en los registros

Soporte
1 
Excepción del trabajo: PG::TRDeadlockDetected: ERROR:  deadlock detected
DETAIL:  Process 29659 waits for ShareLock on transaction 892416679; blocked by process 29650.
Process 29650 waits for ShareLock on transaction 892416541; blocked by process 29659.
HINT:  See server log for query details.
CONTEXT:  while rechecking updated tuple (36923,3) in relation "discourse_activity_pub_actors"

CleanShot 2025-03-27 at 08.57.49@2x
CleanShot 2025-03-27 at 08.57.49@2x1920×500 96.5 KB

Estos aparecen en /logs @angus, no estoy seguro si hay algún problema visible para el usuario. El rastreo de la pila apunta a un trabajo que maneja entregas:

rack-mini-profiler-3.3.1/lib/patches/db/pg.rb:69:in `exec_params'
rack-mini-profiler-3.3.1/lib/patches/db/pg.rb:69:in `exec_params'
(eval at /var/www/discourse/lib/method_profiler.rb:38):105:in `exec_params'
activerecord-7.2.2.1/lib/active_record/connection_adapters/postgresql_adapter.rb:894:in `block (2 levels) in exec_no_cache'
activerecord-7.2.2.1/lib/active_record/connection_adapters/abstract_adapter.rb:1004:in `block in with_raw_connection'
activesupport-7.2.2.1/lib/active_support/concurrency/null_lock.rb:9:in `synchronize'
activerecord-7.2.2.1/lib/active_record/connection_adapters/abstract_adapter.rb:976:in `with_raw_connection'
activerecord-7.2.2.1/lib/active_record/connection_adapters/postgresql_adapter.rb:893:in `block in exec_no_cache'
activesupport-7.2.2.1/lib/active_support/notifications/instrumenter.rb:58:in `instrument'
activerecord-7.2.2.1/lib/active_record/connection_adapters/abstract_adapter.rb:1119:in `log'
activerecord-7.2.2.1/lib/active_record/connection_adapters/postgresql_adapter.rb:892:in `exec_no_cache'
activerecord-7.2.2.1/lib/active_record/connection_adapters/postgresql_adapter.rb:872:in `execute_and_clear'
activerecord-7.2.2.1/lib/active_record/connection_adapters/postgresql/database_statements.rb:79:in `exec_delete'
activerecord-7.2.2.1/lib/active_record/connection_adapters/abstract/database_statements.rb:208:in `update'
activerecord-7.2.2.1/lib/active_record/connection_adapters/abstract/query_cache.rb:27:in `update'
activerecord-7.2.2.1/lib/active_record/relation.rb:610:in `block in update_all'
activerecord-7.2.2.1/lib/active_record/connection_adapters/abstract/connection_pool.rb:421:in `with_connection'
activerecord-7.2.2.1/lib/active_record/connection_handling.rb:296:in `with_connection'
activerecord-7.2.2.1/lib/active_record/relation.rb:598:in `update_all'
/var/www/discourse/plugins/discourse-activity-pub/lib/discourse_activity_pub/delivery_failure_tracker.rb:36:in `set_domain_actors_as_available'
/var/www/discourse/plugins/discourse-activity-pub/lib/discourse_activity_pub/delivery_failure_tracker.rb:22:in `track_success'
/var/www/discourse/plugins/discourse-activity-pub/app/jobs/discourse_activity_pub_deliver.rb:50:in `perform_request'
/var/www/discourse/plugins/discourse-activity-pub/app/jobs/discourse_activity_pub_deliver.rb:15:in `execute'
/var/www/discourse/app/jobs/base.rb:316:in `block (2 levels) in perform'
1 me gusta
3

Esto debería solucionarlo

2 Me gusta
4

Hmm, eso lamentablemente no parece solucionar el problema @angus. Hay muchos actores, posiblemente, en la base de datos, y el procesamiento por lotes sigue siendo insuficiente.

En meta, por ejemplo, hay más de 90k filas en ese modelo:

discourse(prod)> DiscourseActivityPubActor.where(domain: 'mastodon.social').size
=> 90264

¿Necesitamos absolutamente actualizar su columna available en cada entrega?

5

Entendido. Espero que esto, junto con los cambios anteriores, lo solucione:

1 me gusta
6

Este tema se cerró automáticamente después de 20 horas. Ya no se permiten nuevas respuestas.