Celery worker with pickle
serializer and elasticsearch
backend throws SerializationError
when writing to result backend
#8850
Unanswered
william-tremblay1
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
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:
Beta Was this translation helpful? Give feedback.
All reactions