Question

如何处理并发ruby线程池（http://ruby-concurrency.github.io/concurrent-ruby/file.thread_pools.html）中的异常？

示例：

pool = Concurrent::FixedThreadPool.new(5) 
pool.post do
  raise 'something goes wrong'
end

# how to rescue this exception here

更新

以下是我的代码的简化版本：

def process
  pool = Concurrent::FixedThreadPool.new(5)

  products.each do |product|
    new_product = generate_new_product

    pool.post do
      store_in_db(new_product) # here exception is raised, e.g. connection to db failed
    end
  end

  pool.shutdown
  pool.wait_for_terminaton
end

所以我想要实现的是在任何异常的情况下停止处理（中断循环）。

此异常也在更高级别的应用程序中获救，并且执行了一些清理作业（例如将模型状态设置为失败并发送一些通知）。

Answer 1

以下答案来自jdantonio https://github.com/ruby-concurrency/concurrent-ruby/issues/616

＆＃34; 大多数应用程序不应直接使用线程池。线程池是一种用于内部使用的低级抽象。此库中的所有高级抽象（Promise，Actor等）都将作业发布到全局线程池，并且都提供异常处理。只需选择最适合您的用例的抽象并使用它。

如果您觉得需要配置自己的线程池而不是使用全局线程池，您仍然可以使用高级抽象。它们都支持：executor选项，允许您注入自定义线程池。然后，您可以使用高级抽象提供的异常处理。

如果您绝对坚持将作业直接发布到线程池而不是使用我们的高级抽象（我强烈反对），那么只需创建一个作业包装器。您可以在我们所有的高级抽象中找到作业包装器的示例，Rails ActiveJob，Sucker Punch和其他使用我们的线程池的库。＆＃34;

那么使用Promises实现怎么样？ http://ruby-concurrency.github.io/concurrent-ruby/Concurrent/Promise.html 在你的情况下，它看起来像这样：

@Html.DropDownListFor(x => x.Selectedvalue, new SelectList(ViewBag.groepen, "id", "Naam"), "Select", new { @class = "form-control" })

Answer 2

可能有更好的方法，但这确实有效。您需要更改wait_for_pool_to_finish中的错误处理。

def process
  pool = Concurrent::FixedThreadPool.new(10)
  errors = Concurrent::Array.new

  10_000.times do
    pool.post do
      begin
        # do the work
      rescue StandardError => e
        errors << e
      end
    end
  end
  wait_for_pool_to_finish(pool, errors)
end

private

def wait_for_pool_to_finish(pool, errors)
  pool.shutdown

  until pool.shutdown?
    if errors.any?
      pool.kill
      fail errors.first
    end
    sleep 1
  end

  pool.wait_for_termination
end

Answer 3

我创建了一个问题#634。并发线程池可以毫无问题地支持可中断的工作者。

require "concurrent"

Concurrent::RubyThreadPoolExecutor.class_eval do
  # Inspired by "ns_kill_execution".
  def ns_abort_execution aborted_worker
    @pool.each do |worker|
      next if worker == aborted_worker
      worker.kill
    end

    @pool = [aborted_worker]
    @ready.clear

    stopped_event.set
    nil
  end

  def abort_worker worker
    synchronize do
      ns_abort_execution worker
    end
    nil
  end

  def join
    shutdown

    # We should wait for stopped event.
    # We couldn't use timeout.
    stopped_event.wait nil

    @pool.each do |aborted_worker|
      # Rubinius could receive an error from aborted thread's "join" only.
      # MRI Ruby doesn't care about "join".
      # It will receive error anyway.

      # We can "raise" error in aborted thread and than "join" it from this thread.
      # We can "join" aborted thread from this thread and than "raise" error in aborted thread.
      # The order of "raise" and "join" is not important. We will receive target error anyway.

      aborted_worker.join
    end

    @pool.clear
    nil
  end

  class AbortableWorker < self.const_get :Worker
    def initialize pool
      super
      @thread.abort_on_exception = true
    end

    def run_task pool, task, args
      begin
        task.call *args
      rescue StandardError => error
        pool.abort_worker self
        raise error
      end

      pool.worker_task_completed
      nil
    end

    def join
      @thread.join
      nil
    end
  end

  self.send :remove_const, :Worker
  self.const_set :Worker, AbortableWorker
end

class MyError < StandardError; end

pool = Concurrent::FixedThreadPool.new 5

begin
  pool.post do
    sleep 1
    puts "we shouldn't receive this message"
  end

  pool.post do
    puts "raising my error"
    raise MyError
  end

  pool.join

rescue MyError => error
  puts "received my error, trace: \n#{error.backtrace.join("\n")}"
end

sleep 2

输出：

raising my error
received my error, trace:
...

此补丁适用于任何版本的MRI Ruby和Rubinius。 JRuby不工作，我不在乎。如果你想支持它，请修补JRuby执行程序。应该很容易。

处理并发ruby线程池中的异常

3 个答案: