-
Notifications
You must be signed in to change notification settings - Fork 26.9k
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
processChild.js dies in production with no replacement #49623
Comments
https://gist.github.com/masterkain/a3edb77d932fceae51a449082ede65d7 this is the I also fixed |
after some more research I have a rough idea about what is happening
|
the issue for now has been "resolved" by assigning copious amount of ram to each next.js instance. |
jest worker seems really slow; we're noticing ~7s of cold start times. |
This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you. |
Verify canary release
Provide environment information
Operating System: Platform: linux Arch: x64 Version: #1 SMP Tue Sep 13 07:51:46 UTC 2022 Binaries: Node: 20.1.0 npm: 9.6.4 Yarn: 1.22.19 pnpm: N/A Relevant packages: next: 13.4.2-canary.4 eslint-config-next: 13.4.1 react: 18.2.0 react-dom: 18.2.0 typescript: 5.0.4
Which area(s) of Next.js are affected? (leave empty if unsure)
Standalone mode (output: "standalone")
Link to the code that reproduces this issue
To Reproduce
not sure, use prisma?
Describe the Bug
in my next.js 13 appDir app I'm using:
once I started getting some production traffic I started observing lock up issues, timeouts and whatnot.
initially of course I went through the whole prisma/pgbouncer shebang but after some days of debugging (including checking proxied requests between server and jest workers) I just noticed that in my pod just after few requests we observe this.
this is the situation when the server starts, once we get some requests in:
and we can notice how a processChild is missing:
so it seems that a worker crashed but the server still thinks it's around somehow.
on further requests however there are no ECONNRESET in the logs anymore, just the server hanging indefinitely.
it is unclear what is causing this apparent crash given the same pages sometime works, especially when server just restarted.
Expected Behavior
server is stable.
Which browser are you using? (if relevant)
No response
How are you deploying your application? (if relevant)
No response
The text was updated successfully, but these errors were encountered: