-
-
Notifications
You must be signed in to change notification settings - Fork 105
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
"Reply received from MongoDB, but no request was waiting for the result." after 12~ hours #354
Comments
Hey! I don't actively develop the 6.x series of MongoKitten, but given the nature of the bug I've submitted a patch #355 |
Hey, thanks for a quick patch. I will build a new container with that now and report back. |
Update does not seem to have worked unfortunately. I will attempt to investigate it myself over the coming days and submit a PR if I figure it out :) |
@elihwyma is it possible that you're running into MongoKitten's timeouts? |
I really wouldn't think so, I can try adjusting the timeouts. Both Docker containers (app and mongo) are hosted on the same machine 🤷♀️ |
@elihwyma can you check the query times on the local MongoDB instance? I don't think it's a TCP timeout, but a slow query |
@Joannis this may be a monumental me problem. I reset a bunch of stuff and this seemed to work. Some things may be "pointless" but I was trying everything:
|
Are you using change streams? |
Never mind, stopped working at some point.
Can you elaborate please, pretty much everything is default and I don't know much more than that 😅 |
You'd know if you were setting up a change stream. Are you able to join the MongoKitten, Hummingbird or Vapor discord server? I'd love to talk more directly about this |
Describe the bug
When using via Fluent in Vapor, after approximately 12 hours the database will no longer be responsive and the console is littered with messages from MongoKitten.
To Reproduce
Continuously use the same opened database for over (roughly) 12 hours. The timings are an average from Sentry.
Environment:
Additional context
Paired with issue in Fluent: vapor/fluent-mongo-driver#62
The text was updated successfully, but these errors were encountered: