-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
memory issue with where conditions #1642
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
Comments
How much memory does your server have? |
My server has 2G memory (1.3G available at the time) |
Some more ideas to try and identify the problem:
|
Parse.com has own limit, and returns various results, depends on user's installation.
~2.65 M
We use parse for push messages only and we don't have another class.
Nope, single instance only.
Imported from parse database, it should have index.
Somehow, parse server could not apply where clause (I guess)
|
I just put some extra debugging in parse-server and ran locally with the same query. I removed the -G option from the curl and
So it seems there is a problem with extracting the query from URL parameters. |
I think I found the problem and solution. Will attempt a PR |
@steven-supersolid thanks for that. |
It seems to be fixed by #1687, please reopen if the error still occurs |
Yeah, it fixed. I forgot to close this issue. Thanks! |
Environment Setup
Steps to reproduce
When I try to get installation objects with where conditions, parse server fails.
example request:
Logs/Trace
The text was updated successfully, but these errors were encountered: