【问题标题】:Sidekiq jobs not persisting data on a rails appSidekiq 作业没有在 Rails 应用程序上保存数据
【发布时间】:2014-07-16 21:35:59
【问题描述】:

我有以下设置,一个带有 nginx 的 ubuntu 服务器 - 乘客、postgres db、redis 和 sidekiq。

我已经设立了一个新贵工作来密切关注 sidekiq 流程。

description "Sidekiq Background Worker"

# no "start on", we don't want to automatically start
stop on (stopping workers or runlevel [06])

# change to match your deployment user
setuid deploy
setgid deploy

respawn
respawn limit 3 30

# TERM and USR1 are sent by sidekiqctl when stopping sidekiq.  Without declaring these as normal exit codes, it just respawns.
normal exit 0 TERM USR1

script
# this script runs in /bin/sh by default
# respawn as bash so we can source in rbenv
exec /bin/bash <<EOT
  # use syslog for logging
  exec &> /dev/kmsg

  # pull in system rbenv
  export HOME=/home/deploy
  export RAILS_ENV=production
  source /home/deploy/.rvm/scripts/rvm

  cd /home/deploy/myapp/current
  bundle exec sidekiq -c 25 -L log/sidekiq.log -P tmp/pids/sidekiq.pid -q default -q payment -e production
EOT
end script

这实际上是可行的,我可以启动、停止和重新启动该过程。我可以在 sidekiq web http 监视器上看到这个过程。但是当我运行这个工人时,他们会得到处理。这是两个工人:

class EventFinishedWorker
  include Sidekiq::Worker

  def perform(event_id)
    event = Event.find(event_id)
    score_a = event.team_A_score
    score_b = event.team_B_score
    event.bets.each do |bet|
      if (score_a == bet.team_a_score) && (score_b == bet.team_b_score)
        bet.guessed = true
        bet.save
      end
    end
  end

end

class PayPlayersBetsWorker
  include Sidekiq::Worker
  sidekiq_options :queue => :payment

  def perform(event_id)
    event = Event.find(event_id)
    bets = event.bets.where(guessed: true)
    total_winning_bets = bets.count
    unless total_winning_bets == 0
      pot = event.pot
      amount_to_pay = pot / total_winning_bets

       unless bets.empty?
          bets.each do |bet|
            account = bet.user.account
            user = User.find_by_id(bet.user.id)
            bet.payed = true
            bet.save
            account.wincoins += amount_to_pay
            account.accum_wincoins.increment(amount_to_pay)
            account.save
            user.set_score(user.current_score)
          end
       end
    end
  end

end


2014-05-27T18:48:34Z 5985 TID-7agy8 EventFinishedWorker JID-33ef5d7e7de51189d698c1e7 INFO: start
2014-05-27T18:48:34Z 5985 TID-5s4rg PayPlayersBetsWorker JID-e8473aa1bc59f0b958d23509 INFO: start
2014-05-27T18:48:34Z 5985 TID-5s4rg PayPlayersBetsWorker JID-e8473aa1bc59f0b958d23509 INFO: done: 0.07 sec
2014-05-27T18:48:35Z 5985 TID-7agy8 EventFinishedWorker JID-33ef5d7e7de51189d698c1e7 INFO: done: 0.112 sec

我在运行两个工作进程时都没有出错,但是 ...

检查我的数据 EventFinishedWorker 完成了它的工作。没有任何问题。第二份工作 PayPlayersBetsWorker 不起作用。但是当我进入控制台并做类似的事情时。

worker = PayPlayersBetsWorker.new

worker.perform(1)  

它可以完美地运行作业。我还检测到,如果我直接从控制台运行 sidekiq 而不使用新贵,它也可以工作。

bundle exec sidekiq -P tmp/pids/sidekiq.pid -q default -q payment -e production

这行得通。问题似乎与暴发户一起运行sidekiq。帮助将不胜感激:D

【问题讨论】:

    标签: ruby-on-rails ruby jobs sidekiq upstart


    【解决方案1】:

    看起来您在这两个工作之间存在竞争条件。 EFW 未在 PPBW 查询之前完成,没有找到任何内容并立即退出。

    【讨论】:

    • 这正是发生的事情,我在查看日志时意识到了这一点。谢谢你。在另一个工作之前开始工作并不能保证它会以相同的顺序完成:S.
    猜你喜欢
    • 2018-01-08
    • 2017-05-20
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    • 2017-04-26
    • 1970-01-01
    相关资源
    最近更新 更多