Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The MongoDB nodes do not respond properly with large numbers of documents. #10726

Open
Denkard opened this issue Sep 7, 2024 · 4 comments
Open
Labels
in linear Issue or PR has been created in Linear for internal review

Comments

@Denkard
Copy link

Denkard commented Sep 7, 2024

Bug Description

When using MongoDB nodes, I repeatedly encountered the following situation:

image

I'm only using the basics, nothing too complex:

image

The node delivers what it promises, but after completing executions, it no longer responds:

image

To Reproduce

Any large operation with MongoDB nodes

Expected behavior

The node should finish the execution and continue after the requests.

Operating System

Ubuntu 22.04 (Jammy) in Docker Conteiner

n8n Version

1.55.3

Node.js Version

v20.15.0

Database

SQLite (default)

Execution mode

main (default)

@Joffcom
Copy link
Member

Joffcom commented Sep 7, 2024

Hey @Denkard,

We have created an internal ticket to look into this which we will be tracking as "GHC-210"

@Joffcom Joffcom added the in linear Issue or PR has been created in Linear for internal review label Sep 7, 2024
@Joffcom
Copy link
Member

Joffcom commented Sep 9, 2024

Hey @Denkard,

I don't fully understand the issue here, Does the node work and the UI just crashes or does the node stop working? With that many items I would expect the UI to freeze so it may be better to use sub worklfows and split your data up into smaller batches to process.

@Denkard
Copy link
Author

Denkard commented Sep 11, 2024

Hi @Joffcom ! Thanks for the response!

The node stops responding with large amounts of items, regardless of whether it's running through the UI or in the background. The node simply stops responding. I was able to work around the problem by limiting the number of documents and calling the same workflow again.

@Joffcom
Copy link
Member

Joffcom commented Sep 16, 2024

Hye @Denkard,

I wonder if the instance is running out of memory, Does it show any errors when it stops?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in linear Issue or PR has been created in Linear for internal review
Projects
None yet
Development

No branches or pull requests

2 participants