Hi, we are having issues with our server application using Parse Server preventing us to ship more to our production servers (issue is on development servers).
- AWS Elastic Beanstalk (Node.js running on 64bit Amazon Linux/4.9.2 / Node.js 10.16.0) running on an auto-scaling fleet of 1-4 c5.xlarge instances for this application (this is development, never really scales)
- MongoDB database hosted by mLab on a private cluster
- latest functional version was using parse-server v3.4.4
- memory usage goes up until server crashes
- 100% reproducible in our setup
- it takes around 15 to 30 minutes from deploy to crash
What we tried:
- terminate the machine to obtain a new one, same issue
- rollback to our production version using parse-server 3.4.4, this works
- only add back parse-server 3.5.0, the issue happens
- only add back parse-server 3.6.0, the issue happens
- exploring the logs but they are not helpful: nothing in there before the crash and impossible to access the machine once it crashed.
I identified the culprit when updating parse-server from 3.4.4 to 3.5.0 or 3.6.0 (tried both). On the following graph, you can see on the left the memory curve when the server is using parse-server 3.4.4, it grows up then stabilizes around 500MB; on the right when using 3.5.0 or 3.6.0, the memory usage goes up until it reaches the limits of our servers (100% memory used), then the server crashes.
Is anyone else experiencing similar issues? Any idea how to debug this issue?
Happy to provide more information if needed.