Fixed n8n's startup behavior for scaled mode #2242
Merged
Conversation
This file contains 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
|
Thanks a lot. Got merged. |
|
Got released with n8n@0.140.0 |
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.
Some of our community users had issues with n8n when running multiple instances.
Although not officially supported and not the way we recommend scaling n8n, it is a valid approach and this fix also covers a possible problem with our recommended scaling methods.
When initializing multiple n8n instances at once, you have a race condition where all of them will clear the database data, only one will register the webhooks on the database and the others will fail.
Also, when restarting the main process (for example to apply an update), n8n will temporarily stop receiving requests. This fix prevents this from happening.