![](/img/trans.png)
[英]Testing Sidekiq/ActiveJob - Job in ActiveJob but not Sidekiq
[英]Using Sidekiq for Active Job and getting ActiveJob::DeserializationError
我正在尝试使用Sidekiq来完成以下工作。
未排队时执行该作业(perform_now),但在使用Sidekiq调用(perform_later)时失败。
AddEmployeesToRoomJob.perform_now room ## works fine
AddEmployeesToRoomJob.perform_later room ## breaks in Sidekiq
错误:
AddEmployeesToRoomJob JID-da24b13f405b1ece1212bbd5 INFO: fail: 0.003 sec
2016-08-20T14:57:16.645Z 19456 TID-owmym5fbk WARN: {"class":"ActiveJob::QueueAdapters::SidekiqAdapter::JobWrapper","wrapped" :"AddEmployeesToRoomJob","queue":"default","args": [{"job_class":"AddEmployeesToRoomJob","job_id":"0ba5bd30-e281-49a7-a93f- 6e50445183ac","queue_name":"default","priority":null,"arguments": [{"_aj_globalid":"gid://dragonfly/Room/1"}],"locale":"en"}],"retry":true, "jid":"da24b13f405b1ece1212bbd5","created_at":1471704675.739077,"enqueued _at":1471705036.6406531,"error_message":"Error while trying to deserialize arguments: Couldn't find Room with 'id'=1","error_class":"ActiveJob::DeserializationError","failed_at":14717 04675.946183,"retry_count":4,"retried_at":1471705036.644416}
2016-08-20T14:57:16.645Z 19456 TID-owmym5fbk WARN: ActiveJob::DeserializationError: Error while trying to deserialize arguments: Couldn't find Room with 'id'=1
2016-08-20T14:57:16.645Z 19456 TID-owmym5fbk WARN: /Users/tamlyn/.rvm/gems/ruby-2.2.3/gems/activerecord- 5.0.0.1/lib/active_record/relation/finder_methods.rb:357:in `raise_record_not_found_exception!'
我的Job类AddEmployeesToRoomJob <ApplicationJob queue_as:default
def perform(room)
employees = Employee.all
if employees.length > 0
employees.each do |employee|
UserRoom.create(user: employee, room: room)
end
end
end
end
我的想法我不明白为什么它找不到我正在进入执行方法的房间。 就好像它在作业的队列化/ JSON化中以某种方式丢失了该变量?
Sidekiq博士说
“不幸的是,这意味着如果在作业入队后但在调用perform方法之前删除[Room]记录,则异常处理会有所不同。”
他们建议一个解决方法,但我不知道这对我有什么帮助:
rescue_from ActiveJob::DeserializationError do |exception|
# handle a deleted user record
end
在此先感谢您的帮助!
我不认为将Room对象传递给Sidekiq工作者是个好主意。 我总是传递数据库对象的主键,然后重新查询。 尝试这个。
AddEmployeesToRoomJob.perform_later room.id
def perform(room_id)
room = Room.find(room_id)
employees = Employee.all
if employees.length > 0
employees.each do |employee|
UserRoom.create(user: employee, room: room)
end
end
end
end
我自己偶然发现了这个方法,并且发现discard_on
非常有用。 大多数情况下,对删除或从未创建的记录执行作业是非常必要的。
例:
class ApplicationJob < ActiveJob::Base
discard_on ActiveJob::DeserializationError do |job, error|
Rails.logger.error("Skipping job because of ActiveJob::DeserializationError (#{error.message})")
end
end
如果可以确保已提交此模型,则可以将模型传递给作业。 在提交当前事务之前将作业排入队列是一个经典错误。
您可以在此处找到更多信息: https : //github.com/mperham/sidekiq/wiki/FAQ#why-am-i-seeing-a-lot-of-cant-find-modelname-with-id12345-errors-with -sidekiq
在我们的项目中,我们编写了一个模型关注点,以便能够在提交代码块之后添加动态。
module AfterCommitOnce
extend ActiveSupport::Concern
included do
after_commit :execute_after_commit_handlers
end
def after_commit_once(&block)
@after_commits = @after_commits || []
@after_commits << block
end
private
def execute_after_commit_handlers
@after_commits = @after_commits || []
@after_commits.each do |ac|
ac.call
end
@after_commits = []
end
end
将此问题添加到您的Employee
模型中,您可以指定在对数据库提交所有更改后要执行的作业:
...
employee.after_commit_once do
AddEmployeesToRoomJob.perform_later
end
employee.save!
将Ruby对象作为参数发送给sidekick worker是不可取的。 您可以将Id作为参数发送并初始化perform方法中的对象。 如果想要发送对象,那么您可以将Ruby对象转储到任何其他格式,如Json / Binary / yml,如下所示。
object.to_json
要么
Marshal.dump(object)
在使用perform方法中的对象之前,您可以将对象反序列化为Ruby对象,如下所示。
JSON.parse(serialized_object)
要么
Marshal.load(serialized_object)
这些是您的问题的解决方案,但不是理想的解决方案。
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.