Refresh commands over AMQP #4160
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jamesaimonetti
force-pushed
the
maint_via_amqp
branch
from
cb1f7ee
to
a15a33e
Compare
also don't let UntilFun crash the worker
jamesaimonetti
force-pushed
the
maint_via_amqp
branch
from
a15a33e
to
67cb1d6
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Start to build maintenance commands out as AMQP requests. Since apps contains view/fixture/other data, and those apps might not be running where the SUP command is issued, moving to AMQP makes sense to distribute the work to where the data is.
First pass is distributing the refresh work out.