mastodon/app/workers
ThibG 2b1190065c Retry thread resolving (#5599)
Thread resolving is one of the few tasks that isn't retried on failure.
One common cause for failure of this task is a well-connected user replying to
a toot from a little-connected user on a small instance: the small instance
will get many requests at once, and will often fail to answer requests within
the 10 seconds timeout used by Mastodon.

This changes makes the ThreadResolveWorker retry a few times, with a
rapidly-increasing time before retries and large random contribution in order
to spread the load over time.
2017-11-11 16:49:04 +01:00
..
activitypub
…
admin
…
import
…
pubsubhubbub
…
scheduler
…
after_remote_follow_request_worker.rb
…
after_remote_follow_worker.rb
…
authorize_follow_worker.rb
…
block_worker.rb
…
bootstrap_timeline_worker.rb
…
digest_mailer_worker.rb
…
distribution_worker.rb
…
domain_block_worker.rb
…
feed_insert_worker.rb
…
import_worker.rb
…
link_crawl_worker.rb
…
merge_worker.rb
…
notification_worker.rb
…
processing_worker.rb
…
push_update_worker.rb
…
refollow_worker.rb
…
regeneration_worker.rb
…
remote_profile_update_worker.rb
…
removal_worker.rb
…
resolve_remote_account_worker.rb
…
salmon_worker.rb
…
soft_block_domain_followers_worker.rb
…
soft_block_worker.rb
…
thread_resolve_worker.rb Retry thread resolving (#5599) 2017-11-11 16:49:04 +01:00
unfavourite_worker.rb
…
unmerge_worker.rb
…
web_push_notification_worker.rb
…