Enqueue jobs inside a connected_to block
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 25/100
Línea de trabajo
Start by reviewing the database.yml configuration and config/initializers/database.rb, then reproduce SomeJob.perform_later inside the ActiveRecord::Base.connected_to block. Trace how SolidQueue chooses its database connection; done means jobs enqueue through the queue database even when the caller is connected to secondary_shard.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
My rails application connects to multiple databases with the configs below:
database.yml
production:
primary_shard:
...
secondary_shard:
...
queue:
...
config/initializers/database.rb
# This is needed due to us using another gem whose model writes to both primary_shard and secondary_shard and its model inherits from ActiveRecord::Base
ActiveRecord::Base.instance_eval do
connects_to shards: {
primary_shard: {
writing: :primary_shard,
},
secondary_shard: {
writing: :secondary_shard,
},
}
end
SolidQueue has been working well, the only time where we cannot enqueue is if we have a block of code like below:
ActiveRecord::Base.connected_to(role: :writing, shard: :secondary_shard) do
# ...
SomeJob.perform_later(some_argument)
# ...
end
I think it is because SolidQueue is trying to insert the job into secondary_shard instead of the queue database. Is there any way to circumvent this besides rewriting the code to call perform_later outside of the connected_to block? SomeJob.perform_later might be called inside a function with the connected_to block so it's quite a big refactor for us.
- Lenguaje dominante
- Ruby
- Estrellas
- 2.5k
- Forks
- 250
- Merge medio
- 8 h 31 min
- PR fusionados (30 d)
- 5
Guía de contribución
No hay ninguna guía de contribución indexada para este repositorio
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de rails/solid_queue
-
limits_concurrency on_conflict: :discard looking only into running jobs and not blocked jobs Abierto
Dificultad 3/5 1-2 días Aptitud para principiantes 52/100
rails/solid_queue#804 · 1 comentario ·
-
Dificultad 3/5 1-2 días Aptitud para principiantes 35/100
rails/solid_queue#802 ·
-
Dificultad 5/5 Más de una semana Aptitud para principiantes 35/100
rails/solid_queue#797 ·
-
Dificultad 4/5 3-5 días Aptitud para principiantes 55/100
rails/solid_queue#792 · 1 reacción ·
-
Let `bin/jobs check` validate a config for an env it isn't running in, and without a database Abierto
Dificultad 4/5 3-5 días Aptitud para principiantes 52/100
rails/solid_queue#780 ·
Todos los issues de rails/solid_queue
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
TheOdinProject/curriculum#31417 · 2 comentarios ·
-
Allow faraday-http-cache 3.x Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
glossarist/glossarist-ruby#238 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
palladius/rails8-app-on-gcp#145 ·