fix(core): Disconnect Redis after pausing queue during worker shutdown #9928
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.
Summary
During shutdown
BaseCommand.onTerminationSignal
callsShutdownService.shutdown
which eventually callsRedisClientService.disconnectClients
and in parallelWorker.stopProcess
pauses the queue withjobQueue.pause
. If we try to pause after having disconnected, this can lead toError from queue
.Hence call
disconnectClients
only after pausing the queue and after waiting for the active executions to finish. Incidentally also move the warningRedis unavailable - trying to reconnect...
from the client'sclose
event to the retry strategy to prevent confusion.Related Linear tickets, Github issues, and Community forum posts
https://n8nio.slack.com/archives/C069YF49G8Y/p1720000315032489
Review / Merge checklist
release/backport
(if the PR is an urgent fix that needs to be backported)