Closed sentry-io[bot] closed 3 years ago
Sentry issue: RED-HAT-0P-2VW
This issue has been marked as stale because it hasn't seen any activity for the last 60 days.
Stale issues are closed after 14 days, unless the label is removed by a maintainer or someone comments on it.
This is done in order to ensure that open issues are still relevant.
Thank you for your contribution! :unicorn: :rocket: :robot:
(Note: issues labeled with pinned or EPIC are never marked as stale.)
@jpopelka this is still not fixed and related to the global worker architecture, isn't it?
Yes, we haven't investigated that yet and still need to know how to work around that if ever wanted to move to SQS.
This issue has been marked as stale because it hasn't seen any activity for the last 60 days.
Stale issues are closed after 14 days, unless the label is removed by a maintainer or someone comments on it.
This is done in order to ensure that open issues are still relevant.
Thank you for your contribution! :unicorn: :rocket: :robot:
(Note: issues labeled with pinned or EPIC are never marked as stale.)
This issue has been marked as stale because it hasn't seen any activity for the last 60 days.
Stale issues are closed after 14 days, unless the label is removed by a maintainer or someone comments on it.
This is done in order to ensure that open issues are still relevant.
Thank you for your contribution! :unicorn: :rocket: :robot:
(Note: issues labeled with pinned or EPIC are never marked as stale.)
I did some searching and all advice (example) I found suggest storing the message in a DB (S3) and send only pointer to the data in the actual message to SQS. I haven't found anything that would help us with this in Python, the official library for this purpose is in Java only. Even I found one post which points to a python example project which should do this, I haven't found anything like that in the code itself. Since in our case it's Celery sending/consuming the message we would probably need to extend some Celery classes.
This issue has been marked as stale because it hasn't seen any activity for the last 60 days.
Stale issues are closed after 14 days, unless the label is removed by a maintainer or someone comments on it.
This is done in order to ensure that open issues are still relevant.
Thank you for your contribution! :unicorn: :rocket: :robot:
(Note: issues labeled with pinned or EPIC are never marked as stale.)
It seems we won't use the AWS' native services after all in the near future so I'm going to close this.
Sentry Issue: RED-HAT-0P-2V8