fix: handle decode errors#375
Merged
Merged
Conversation
When a message fails to be decoded the consumer thread can't do anything to recovery it because the message has not been created yet. To prevents the worker consumer thread to continuously break, this change try to handle any error from decode and nack the message.
eduardogspereira
approved these changes
Jan 18, 2021
Owner
|
Thanks! |
This file contains hidden or 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
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.
I noticed that the worker consumer thread hangs indefinitely when an exception is raised from the message decoder. The consumer does not know how to handle it because the message has not been created yet.
So it enters in the loop:
I tried to follow the suggested approach presented in #284, but I couldn't make it work.
I think the encode side is safe because we can handle exceptions on the publisher side.
--
Note that the PR changes only applies to RabbitMQ broker. For Redis, I used the
JSONEncoderas a fallback to accessredis_message_idand rejects the message since it is not available after the exception occurs. But I don't know if it's the right approach.Log from consumer thread
worker.py 275 CRITICAL Consumer encountered an unexpected error. Traceback (most recent call last): File "/home/thomaz/dev/python/dramatiq/dramatiq/worker.py", line 259, in run for message in self.consumer: File "/home/thomaz/dev/python/dramatiq/dramatiq/brokers/rabbitmq.py", line 492, in __next__ message = Message.decode(body) File "/home/thomaz/dev/python/dramatiq/dramatiq/message.py", line 96, in decode return cls(**global_encoder.decode(data)) File "/home/thomaz/dev/python/dramatiq/tests/test_rabbitmq.py", line 471, in decode raise RuntimeError("xfail") RuntimeError: xfail [2021-01-18 13:24:37,328] [Thread-35] [dramatiq.worker.ConsumerThread(default)] [INFO] Restarting consumer in 3.00 seconds. [2021-01-18 13:24:37,328] [Thread-35] [dramatiq.brokers.rabbitmq._RabbitmqConsumer] [ERROR] Failed to wait for all callbacks to complete. This can happen when the RabbitMQ server is suddenly restarted. Traceback (most recent call last): File "/home/thomaz/dev/python/dramatiq/dramatiq/brokers/rabbitmq.py", line 507, in close self.connection.add_callback_threadsafe(all_callbacks_handled.set) File "/home/thomaz.soares/.virtualenvs/dramatiq/lib/python3.7/site-packages/pika/adapters/blocking_connection.py", line 744, in add_callback_threadsafe 'BlockingConnection.add_callback_threadsafe() called on ' pika.exceptions.ConnectionWrongStateError: BlockingConnection.add_callback_threadsafe() called on closed or closing connection. rabbitmq.py 512 ERROR Failed to wait for all callbacks to complete. This can happen when the RabbitMQ server is suddenly restarted. Traceback (most recent call last): File "/home/thomaz/dev/python/dramatiq/dramatiq/brokers/rabbitmq.py", line 507, in close self.connection.add_callback_threadsafe(all_callbacks_handled.set) File "/home/thomaz.soares/.virtualenvs/dramatiq/lib/python3.7/site-packages/pika/adapters/blocking_connection.py", line 744, in add_callback_threadsafe 'BlockingConnection.add_callback_threadsafe() called on ' pika.exceptions.ConnectionWrongStateError: BlockingConnection.add_callback_threadsafe() called on closed or closing connection. [2021-01-18 13:24:40,347] [Thread-35] [dramatiq.worker.ConsumerThread(default)] [CRITICAL] Consumer encountered an unexpected error. Traceback (most recent call last): File "/home/thomaz/dev/python/dramatiq/dramatiq/worker.py", line 259, in run for message in self.consumer: File "/home/thomaz/dev/python/dramatiq/dramatiq/brokers/rabbitmq.py", line 492, in __next__ message = Message.decode(body) File "/home/thomaz/dev/python/dramatiq/dramatiq/message.py", line 96, in decode return cls(**global_encoder.decode(data)) File "/home/thomaz/dev/python/dramatiq/tests/test_rabbitmq.py", line 471, in decode raise RuntimeError("xfail") RuntimeError: xfail