Use rq_redis_connection when listing RQ jobs in remove_ghost_locks maintenance task #6539
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.
What type of PR is this?
Description
Fix for UnicodeDecodeError in remove_ghost_locks mainentance task.
Redash has two connections to Redis - one for RQ, which does not support decode_responses in it's connection string, and one for Redash direct access to Redis, which expects decode_responses to be set. There is one place in the remove_ghost_locks call stack where the Redash connection is used in place of the RQ one, causing UnicodeDecodeErrors.
Discovered while investigating #6424
How is this tested?
worker
instead ofdev_worker
(to make the healthcheck tasks run)SELECT pg_sleep(300)
)UnicodeDecodeError: 'utf-8' codec can't decode byte 0x9c in position 1: invalid start byte
in docker logs ofredash-worker-1
during query executionUnicodeDecodeError
inredash-worker-1
logs