Skip to content

Split up Sidekiq work across more specific queues. #422 #247

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 25, 2014

Conversation

codebender
Copy link
Contributor

Split up Sidekiq work across more specific queues. #422

New sidekiq queues & priorities:

  • event_tracker - 5
  • index - 4
  • timeline - 3
  • search_sync - 2
  • user - 2
  • data_cleanup - 1
  • event_publisher - 1
  • github - 1
  • mailer - 1
  • network - 1
  • protip - 1
  • team - 1

ℹ️ A 2nd PR that removes the old queues from sidekiq.yml will need to be created after this is deployed to production. Jobs queued up during the deploy still need to be worked, that is why the OLD queues are not removed by this PR. Once the OLD queues are worked & emptied, then the 2nd PR can merged and deployed ℹ️

https://assembly.com/coderwall/bounties/422

SearchSyncJob must use search_sync queue for uniqueness

SearchSyncJob depends on its queue being its own queue, because that is
how it enforces uniqueness
@codebender codebender force-pushed the reorg_sidekiq_queues_422 branch 2 times, most recently from 5d229d7 to d057062 Compare November 21, 2014 18:52
just3ws added a commit that referenced this pull request Nov 25, 2014
Split up Sidekiq work across more specific queues. #422
@just3ws just3ws merged commit 8b75c52 into coderwall:master Nov 25, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants