-
Notifications
You must be signed in to change notification settings - Fork 27
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
✨ Add a Distributed Task Queue (using Celery) #7214
base: master
Are you sure you want to change the base?
✨ Add a Distributed Task Queue (using Celery) #7214
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #7214 +/- ##
===========================================
- Coverage 87.17% 66.79% -20.39%
===========================================
Files 1680 725 -955
Lines 65053 34181 -30872
Branches 1106 177 -929
===========================================
- Hits 56709 22830 -33879
- Misses 8030 11289 +3259
+ Partials 314 62 -252
*This pull request uses carry forward flags. Click here to find out more.
Continue to review full report in Codecov by Sentry.
|
…o/osparc-simcore into add-distributed-task-queue
|
What do these changes do?
Introduce a Distributed Task Queue (using Celery). On the first iteration it will be used by Storage service for file compression.
The Storage now works on 2 modes:
STANDARD
andWORKER
.In the
STANDARD
mode, the service uses Celery to submit tasks and get progress/results.In the
WORKER
mode, it is executed as Celery worker (with FastAPI intitialized) and it is responsible for tasks execution.Related issue/s
storage
dummy rpc endpoints for zipping #7202How to test
Dev-ops checklist