You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Originally posted by william-tremblay1 February 14, 2024
It seems that when using Celery with pickle serialization and Elasticsearch as a backend, the ElasticsearchBackend tries to set the field of a JSON body to a pickle-encoded bytes object directly, which leads to a serialization error. This is the throwing code:
Discussed in #8850
Originally posted by william-tremblay1 February 14, 2024
It seems that when using Celery with pickle serialization and Elasticsearch as a backend, the
ElasticsearchBackend
tries to set the field of a JSON body to a pickle-encodedbytes
object directly, which leads to a serialization error. This is the throwing code:celery/celery/backends/elasticsearch.py
Lines 128 to 142 in 7528900
Here are my Celery serialization configuration options.
Is this a bug or a misconfiguration?
Logs:
The text was updated successfully, but these errors were encountered: