Don't log when queue is unavailable

Fixes #1223

For large chains like ETH Mainnet, it is fairly common for the catchup
fetcher to take a long time to calculate the missing block numbers and
start the named Sequence used by `push_front(block)`.  Since this is
normal and not exceptional, `InvalidConsensus.Worker` shouldn't log this
and retry silently.
pull/1224/head
Luke Imhoff 6 years ago
parent f7b89123d6
commit c978b6168b
  1. 5
      apps/indexer/lib/indexer/block/invalid_consensus/worker.ex

@ -77,7 +77,10 @@ defmodule Indexer.Block.InvalidConsensus.Worker do
end end
def handle_info({ref, {:error, reason}}, %{task_ref: ref, retry_interval: millis} = state) do def handle_info({ref, {:error, reason}}, %{task_ref: ref, retry_interval: millis} = state) do
Logger.error(fn -> inspect(reason) end) case reason do
:queue_unavailable -> :ok
_ -> Logger.error(fn -> inspect(reason) end)
end
Process.demonitor(ref, [:flush]) Process.demonitor(ref, [:flush])
Process.send_after(self(), :push_front_blocks, millis) Process.send_after(self(), :push_front_blocks, millis)

Loading…
Cancel
Save